CVE-2020-24345

JerryScript through 2.3.0 allows stack consumption via function a(){new new Proxy(a,{})}JSON.parse("[]",a). NOTE: the vendor states that the problem is the lack of the --stack-limit option

CVSS v3 7.8 HIGH
CVSS v2.0 6.8 MEDIUM

7.8^/10

CVSS v3 : HIGH

Vector :

Exploitability : 1.8 / Impact : 5.9

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required NONE

User Interaction REQUIRED

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

6.8^/10

CVSS v2.0 : MEDIUM

Vector : AV:N/AC:M/Au:N/C:P/I:P/A:P

Exploitability : 8.6 / Impact : 6.4

Access Vector NETWORK

Access Complexity MEDIUM

Authentication NONE

Confidentiality Impact PARTIAL

Integrity Impact PARTIAL

Availability Impact PARTIAL

References

Link	Resource
https://github.com/jerryscript-project/jerryscript/issues/3977	Exploit Issue Tracking Patch Third Party Advisory

Configurations

Configuration 1 (hide)

cpe:2.3:a:jerryscript:jerryscript:*:*:*:*:*:*:*:*

History

No history.

Information

Published : 2020-08-13 19:15

Updated : 2024-05-17 01:45

NVD link : CVE-2020-24345

Mitre link : CVE-2020-24345

CVE.ORG link : CVE-2020-24345

JSON object : View

Products Affected

jerryscript

jerryscript

CWE

CWE-787

Out-of-bounds Write

{"id": "CVE-2020-24345", "cveTags": [{"tags": ["disputed"], "sourceIdentifier": "cve@mitre.org"}], "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 6.8, "accessVector": "NETWORK", "vectorString": "AV:N/AC:M/Au:N/C:P/I:P/A:P", "authentication": "NONE", "integrityImpact": "PARTIAL", "accessComplexity": "MEDIUM", "availabilityImpact": "PARTIAL", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 6.4, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 8.6, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": true}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.8, "attackVector": "LOCAL", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 1.8}]}, "published": "2020-08-13T19:15:13.807", "references": [{"url": "https://github.com/jerryscript-project/jerryscript/issues/3977", "tags": ["Exploit", "Issue Tracking", "Patch", "Third Party Advisory"], "source": "cve@mitre.org"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-787"}]}], "descriptions": [{"lang": "en", "value": "JerryScript through 2.3.0 allows stack consumption via function a(){new new Proxy(a,{})}JSON.parse(\"[]\",a). NOTE: the vendor states that the problem is the lack of the --stack-limit option"}, {"lang": "es", "value": "** EN DISPUTA** JerryScript versiones hasta 2.3.0, permite un consumo de pila por medio de la funci\u00f3n a(){new new Proxy(a,{})}JSON.parse(\"[]\",a). NOTA: el proveedor afirma que el problema es la falta de la opci\u00f3n --stack-limit"}], "lastModified": "2024-05-17T01:45:47.737", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:jerryscript:jerryscript:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "01F91CD4-9EFF-4338-A18E-64F109090995", "versionEndIncluding": "2.3.0"}], "operator": "OR"}]}], "sourceIdentifier": "cve@mitre.org"}