CVE-2023-39532 (GCVE-0-2023-39532)
Vulnerability from cvelistv5 – Published: 2023-08-08 16:51 – Updated: 2024-10-10 18:39- CWE-20 - Improper Input Validation
| URL | Tags |
|---|---|
| https://github.com/endojs/endo/security/advisorie… | x_refsource_CONFIRM |
| https://github.com/endojs/endo/commit/fc90c642960… | x_refsource_MISC |
{
"containers": {
"adp": [
{
"providerMetadata": {
"dateUpdated": "2024-08-02T18:10:21.174Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"name": "https://github.com/endojs/endo/security/advisories/GHSA-9c4h-3f7h-322r",
"tags": [
"x_refsource_CONFIRM",
"x_transferred"
],
"url": "https://github.com/endojs/endo/security/advisories/GHSA-9c4h-3f7h-322r"
},
{
"name": "https://github.com/endojs/endo/commit/fc90c6429604dc79ce8e3355e236ccce2bada041",
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://github.com/endojs/endo/commit/fc90c6429604dc79ce8e3355e236ccce2bada041"
}
],
"title": "CVE Program Container"
},
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2023-39532",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-10-10T18:38:26.015416Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2024-10-10T18:39:02.981Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "endo",
"vendor": "endojs",
"versions": [
{
"status": "affected",
"version": "\u003e= 0.18.0, \u003c 0.18.7"
},
{
"status": "affected",
"version": "= 0.17.0"
},
{
"status": "affected",
"version": "= 0.16.0"
},
{
"status": "affected",
"version": "\u003e= 0.15.0, \u003c 0.15.24"
},
{
"status": "affected",
"version": "\u003e= 0.14.0, \u003c 0.14.5"
},
{
"status": "affected",
"version": "\u003e= 0.13.0, \u003c 0.13.5"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "SES is a JavaScript environment that allows safe execution of arbitrary programs in Compartments. In version 0.18.0 prior to 0.18.7, 0.17.0 prior to 0.17.1, 0.16.0 prior to 0.16.1, 0.15.0 prior to 0.15.24, 0.14.0 prior to 0.14.5, an 0.13.0 prior to 0.13.5, there is a hole in the confinement of guest applications under SES that may manifest as either the ability to exfiltrate information or execute arbitrary code depending on the configuration and implementation of the surrounding host.\n\nGuest program running inside a Compartment with as few as no endowments can gain access to the surrounding host\u2019s dynamic import by using dynamic import after the spread operator, like `{...import(arbitraryModuleSpecifier)}`.\n\nOn the web or in web extensions, a Content-Security-Policy following ordinary best practices likely mitigates both the risk of exfiltration and execution of arbitrary code, at least limiting the modules that the attacker can import to those that are already part of the application. However, without a Content-Security-Policy, dynamic import can be used to issue HTTP requests for either communication through the URL or for the execution of code reachable from that origin.\n\nWithin an XS worker, an attacker can use the host\u2019s module system to the extent that the host has been configured. This typically only allows access to module code on the host\u2019s file system and is of limited use to an attacker.\n\nWithin Node.js, the attacker gains access to Node.js\u2019s module system. Importing the powerful builtins is not useful except insofar as there are side-effects and tempered because dynamic import returns a promise. Spreading a promise into an object renders the promises useless. However, Node.js allows importing data URLs, so this is a clear path to arbitrary execution.\n\nVersions 0.18.7, 0.17.1, 0.16.1, 0.15.24, 0.14.5, and 0.13.5 contain a patch for this issue. Some workarounds are available. On the web, providing a suitably constrained Content-Security-Policy mitigates most of the threat. With XS, building a binary that lacks the ability to load modules at runtime mitigates the entirety of the threat. That will look like an implementation of `fxFindModule` in a file like `xsPlatform.c` that calls `fxRejectModuleFile`."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-20",
"description": "CWE-20: Improper Input Validation",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2023-08-08T16:51:26.262Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/endojs/endo/security/advisories/GHSA-9c4h-3f7h-322r",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/endojs/endo/security/advisories/GHSA-9c4h-3f7h-322r"
},
{
"name": "https://github.com/endojs/endo/commit/fc90c6429604dc79ce8e3355e236ccce2bada041",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/endojs/endo/commit/fc90c6429604dc79ce8e3355e236ccce2bada041"
}
],
"source": {
"advisory": "GHSA-9c4h-3f7h-322r",
"discovery": "UNKNOWN"
},
"title": "SES\u0027s dynamic import and spread operator provides possible path to arbitrary exfiltration and execution"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2023-39532",
"datePublished": "2023-08-08T16:51:26.262Z",
"dateReserved": "2023-08-03T16:27:36.263Z",
"dateUpdated": "2024-10-10T18:39:02.981Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2023-39532",
"date": "2026-11-15",
"epss": "0.01349",
"percentile": "0.71941"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"product": "endo",
"vendor": "endojs",
"versions": [
{
"status": "affected",
"version": "\u003e= 0.18.0, \u003c 0.18.7"
},
{
"status": "affected",
"version": "= 0.17.0"
},
{
"status": "affected",
"version": "= 0.16.0"
},
{
"status": "affected",
"version": "\u003e= 0.15.0, \u003c 0.15.24"
},
{
"status": "affected",
"version": "\u003e= 0.14.0, \u003c 0.14.5"
},
{
"status": "affected",
"version": "\u003e= 0.13.0, \u003c 0.13.5"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:agoric:ses:*:*:*:*:*:node.js:*:*",
"matchCriteriaId": "4E1EC633-C037-4C04-871D-8A99CC95341E",
"versionEndExcluding": "0.13.5",
"versionStartIncluding": "0.13.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:agoric:ses:*:*:*:*:*:node.js:*:*",
"matchCriteriaId": "FE092E36-42AD-4ECB-9D1D-1F055255E807",
"versionEndExcluding": "0.14.5",
"versionStartIncluding": "0.14.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:agoric:ses:*:*:*:*:*:node.js:*:*",
"matchCriteriaId": "E5511281-9D66-439E-999A-EB5EEEA5C4C2",
"versionEndExcluding": "0.15.24",
"versionStartIncluding": "0.15.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:agoric:ses:*:*:*:*:*:node.js:*:*",
"matchCriteriaId": "BABF5176-1760-461C-9B4F-C16D499C7F5F",
"versionEndExcluding": "0.18.7",
"versionStartIncluding": "0.18.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:agoric:ses:0.16.0:*:*:*:*:node.js:*:*",
"matchCriteriaId": "530B00E7-D900-4C6B-8078-C163041FF77A",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:agoric:ses:0.17.0:*:*:*:*:node.js:*:*",
"matchCriteriaId": "35FEBC71-1F8D-4B91-95CA-3FB5F051450D",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "SES is a JavaScript environment that allows safe execution of arbitrary programs in Compartments. In version 0.18.0 prior to 0.18.7, 0.17.0 prior to 0.17.1, 0.16.0 prior to 0.16.1, 0.15.0 prior to 0.15.24, 0.14.0 prior to 0.14.5, an 0.13.0 prior to 0.13.5, there is a hole in the confinement of guest applications under SES that may manifest as either the ability to exfiltrate information or execute arbitrary code depending on the configuration and implementation of the surrounding host.\n\nGuest program running inside a Compartment with as few as no endowments can gain access to the surrounding host\u2019s dynamic import by using dynamic import after the spread operator, like `{...import(arbitraryModuleSpecifier)}`.\n\nOn the web or in web extensions, a Content-Security-Policy following ordinary best practices likely mitigates both the risk of exfiltration and execution of arbitrary code, at least limiting the modules that the attacker can import to those that are already part of the application. However, without a Content-Security-Policy, dynamic import can be used to issue HTTP requests for either communication through the URL or for the execution of code reachable from that origin.\n\nWithin an XS worker, an attacker can use the host\u2019s module system to the extent that the host has been configured. This typically only allows access to module code on the host\u2019s file system and is of limited use to an attacker.\n\nWithin Node.js, the attacker gains access to Node.js\u2019s module system. Importing the powerful builtins is not useful except insofar as there are side-effects and tempered because dynamic import returns a promise. Spreading a promise into an object renders the promises useless. However, Node.js allows importing data URLs, so this is a clear path to arbitrary execution.\n\nVersions 0.18.7, 0.17.1, 0.16.1, 0.15.24, 0.14.5, and 0.13.5 contain a patch for this issue. Some workarounds are available. On the web, providing a suitably constrained Content-Security-Policy mitigates most of the threat. With XS, building a binary that lacks the ability to load modules at runtime mitigates the entirety of the threat. That will look like an implementation of `fxFindModule` in a file like `xsPlatform.c` that calls `fxRejectModuleFile`."
}
],
"id": "CVE-2023-39532",
"lastModified": "2026-06-17T06:12:32.113",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "security-advisories@github.com",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2023-39532",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "yes"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-10-10T18:38:26.015416Z",
"version": "2.0.3"
}
}
]
},
"published": "2023-08-08T17:15:09.607",
"references": [
{
"source": "security-advisories@github.com",
"tags": [
"Patch"
],
"url": "https://github.com/endojs/endo/commit/fc90c6429604dc79ce8e3355e236ccce2bada041"
},
{
"source": "security-advisories@github.com",
"tags": [
"Exploit",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/endojs/endo/security/advisories/GHSA-9c4h-3f7h-322r"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/endojs/endo/commit/fc90c6429604dc79ce8e3355e236ccce2bada041"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/endojs/endo/security/advisories/GHSA-9c4h-3f7h-322r"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-20"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
},
{
"description": [
{
"lang": "en",
"value": "NVD-CWE-noinfo"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
},
"redhat_vex": {
"current_release_date": "2025-05-28T23:31:16+00:00",
"cve": "CVE-2023-39532",
"id": "CVE-2023-39532",
"initial_release_date": "2023-01-01T00:00:00+00:00",
"product_status:known_not_affected": "1",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "SES\u0027s dynamic import and spread operator provides possible path to arbitrary exfiltration and execution",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2023/cve-2023-39532.json",
"version": "3"
},
"vulnrichment": {
"containers": {
"adp": [
{
"providerMetadata": {
"dateUpdated": "2024-08-02T18:10:21.174Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"name": "https://github.com/endojs/endo/security/advisories/GHSA-9c4h-3f7h-322r",
"tags": [
"x_refsource_CONFIRM",
"x_transferred"
],
"url": "https://github.com/endojs/endo/security/advisories/GHSA-9c4h-3f7h-322r"
},
{
"name": "https://github.com/endojs/endo/commit/fc90c6429604dc79ce8e3355e236ccce2bada041",
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://github.com/endojs/endo/commit/fc90c6429604dc79ce8e3355e236ccce2bada041"
}
],
"title": "CVE Program Container"
},
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2023-39532",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-10-10T18:38:26.015416Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2024-10-10T18:38:39.184Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "endo",
"vendor": "endojs",
"versions": [
{
"status": "affected",
"version": "\u003e= 0.18.0, \u003c 0.18.7"
},
{
"status": "affected",
"version": "= 0.17.0"
},
{
"status": "affected",
"version": "= 0.16.0"
},
{
"status": "affected",
"version": "\u003e= 0.15.0, \u003c 0.15.24"
},
{
"status": "affected",
"version": "\u003e= 0.14.0, \u003c 0.14.5"
},
{
"status": "affected",
"version": "\u003e= 0.13.0, \u003c 0.13.5"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "SES is a JavaScript environment that allows safe execution of arbitrary programs in Compartments. In version 0.18.0 prior to 0.18.7, 0.17.0 prior to 0.17.1, 0.16.0 prior to 0.16.1, 0.15.0 prior to 0.15.24, 0.14.0 prior to 0.14.5, an 0.13.0 prior to 0.13.5, there is a hole in the confinement of guest applications under SES that may manifest as either the ability to exfiltrate information or execute arbitrary code depending on the configuration and implementation of the surrounding host.\n\nGuest program running inside a Compartment with as few as no endowments can gain access to the surrounding host\u2019s dynamic import by using dynamic import after the spread operator, like `{...import(arbitraryModuleSpecifier)}`.\n\nOn the web or in web extensions, a Content-Security-Policy following ordinary best practices likely mitigates both the risk of exfiltration and execution of arbitrary code, at least limiting the modules that the attacker can import to those that are already part of the application. However, without a Content-Security-Policy, dynamic import can be used to issue HTTP requests for either communication through the URL or for the execution of code reachable from that origin.\n\nWithin an XS worker, an attacker can use the host\u2019s module system to the extent that the host has been configured. This typically only allows access to module code on the host\u2019s file system and is of limited use to an attacker.\n\nWithin Node.js, the attacker gains access to Node.js\u2019s module system. Importing the powerful builtins is not useful except insofar as there are side-effects and tempered because dynamic import returns a promise. Spreading a promise into an object renders the promises useless. However, Node.js allows importing data URLs, so this is a clear path to arbitrary execution.\n\nVersions 0.18.7, 0.17.1, 0.16.1, 0.15.24, 0.14.5, and 0.13.5 contain a patch for this issue. Some workarounds are available. On the web, providing a suitably constrained Content-Security-Policy mitigates most of the threat. With XS, building a binary that lacks the ability to load modules at runtime mitigates the entirety of the threat. That will look like an implementation of `fxFindModule` in a file like `xsPlatform.c` that calls `fxRejectModuleFile`."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-20",
"description": "CWE-20: Improper Input Validation",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2023-08-08T16:51:26.262Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/endojs/endo/security/advisories/GHSA-9c4h-3f7h-322r",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/endojs/endo/security/advisories/GHSA-9c4h-3f7h-322r"
},
{
"name": "https://github.com/endojs/endo/commit/fc90c6429604dc79ce8e3355e236ccce2bada041",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/endojs/endo/commit/fc90c6429604dc79ce8e3355e236ccce2bada041"
}
],
"source": {
"advisory": "GHSA-9c4h-3f7h-322r",
"discovery": "UNKNOWN"
},
"title": "SES\u0027s dynamic import and spread operator provides possible path to arbitrary exfiltration and execution"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2023-39532",
"datePublished": "2023-08-08T16:51:26.262Z",
"dateReserved": "2023-08-03T16:27:36.263Z",
"dateUpdated": "2024-10-10T18:39:02.981Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.