CWE-284
DiscouragedImproper Access Control
Abstraction: Pillar · Status: Incomplete
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
7802 vulnerabilities reference this CWE, most recent first.
GHSA-V8F2-2GHQ-9WHV
Vulnerability from github – Published: 2026-07-03 21:31 – Updated: 2026-07-06 18:30Gitea versions before 1.25.5 accept malformed or injected forwarded-proto values when detecting public URLs, allowing spoofed canonical URL generation.
{
"affected": [],
"aliases": [
"CVE-2026-27779"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-03T21:16:59Z",
"severity": "HIGH"
},
"details": "Gitea versions before 1.25.5 accept malformed or injected forwarded-proto values when detecting public URLs, allowing spoofed canonical URL generation.",
"id": "GHSA-v8f2-2ghq-9whv",
"modified": "2026-07-06T18:30:57Z",
"published": "2026-07-03T21:31:38Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27779"
},
{
"type": "WEB",
"url": "https://github.com/go-gitea/gitea/pull/36810"
},
{
"type": "WEB",
"url": "https://github.com/go-gitea/gitea/pull/36836"
},
{
"type": "WEB",
"url": "https://blog.gitea.com/release-of-1.25.5"
},
{
"type": "WEB",
"url": "https://github.com/go-gitea/gitea/releases/tag/v1.25.5"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-V8F2-89XW-2297
Vulnerability from github – Published: 2024-04-15 06:30 – Updated: 2024-04-15 06:30The password reset feature of Ai3 QbiBot lacks proper access control, allowing unauthenticated remote attackers to reset any user's password.
{
"affected": [],
"aliases": [
"CVE-2024-3777"
],
"database_specific": {
"cwe_ids": [
"CWE-284",
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-04-15T04:15:16Z",
"severity": "CRITICAL"
},
"details": "\nThe password reset feature of Ai3 QbiBot lacks proper access control, allowing unauthenticated remote attackers to reset any user\u0027s password.\n\n",
"id": "GHSA-v8f2-89xw-2297",
"modified": "2024-04-15T06:30:34Z",
"published": "2024-04-15T06:30:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-3777"
},
{
"type": "WEB",
"url": "https://www.twcert.org.tw/tw/cp-132-7732-9a54e-1.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-V8FW-85R8-5M23
Vulnerability from github – Published: 2026-06-16 19:09 – Updated: 2026-06-16 19:09Summary
Deno's network permission model is designed so that --deny-net rules apply to the resolved IP address of a destination, not just the literal string supplied by the caller. That means --deny-net=127.0.0.1 (or --deny-net=127.0.0.0/8) is expected to block any attempt to reach loopback, regardless of how the hostname is spelled.
On affected versions, the Node.js compatibility TCP path checked the permission against the original hostname string before resolution and then did not re-check after resolution. A caller could therefore pass a numeric alias of an IP address (for example the decimal integer 2130706433 or the hex form 0x7f000001, both of which resolve to 127.0.0.1) and reach the denied destination through node:net.connect or node:http.request's { host, port } options form.
The native Deno.connect(), fetch(), and URL-string variants of node:http.request("http://...") were not affected, because they either re-checked permissions after resolution or normalized the hostname through the URL parser before checking.
Proof of concept
Run on Deno 2.7.14, with a local TCP listener on 127.0.0.1:<PORT>:
import net from "node:net";
// --allow-net + --deny-net=127.0.0.0/8
// (or even --deny-net=127.0.0.1:<PORT>)
net.connect({ host: "2130706433", port: PORT }); // CONNECTED ❌
net.connect({ host: "0x7f000001", port: PORT }); // CONNECTED ❌
net.connect({ host: "127.0.0.1", port: PORT }); // denied ✅
The same primitive reached the loopback HTTP listener through node:http when the destination was passed as options rather than as a URL string:
import http from "node:http";
// options-form host — bypasses the deny rule on affected versions
http.request({ hostname: "2130706433", port: PORT, path: "/" }).end();
// URL-string form — correctly denied (URL parser normalizes the host)
http.request(`http://2130706433:${PORT}/`).end();
The server-side log showed the bypassed requests arriving from 127.0.0.1 with the numeric alias preserved in the Host header.
Impact
A program that intentionally allows broad outbound network access but uses --deny-net to carve out protected destinations, typically loopback, private/internal ranges, or cloud-instance metadata IPs, could be made to reach those denied destinations from less-trusted code (a dependency, plugin, or attacker-controlled input) that funnels through node:net.connect({ host }) or node:http.request({ hostname }).
The CVSS vector reflects this as a local-attack-vector, permissions-required confidentiality impact: the attacker needs to be able to run code inside the Deno process, and the demonstrated primitive is "reach an explicitly denied IP." It does not by itself exfiltrate data or execute code; the further impact depends on what the now-reachable endpoint exposes.
The confirmed scope is IPv4 numeric hostname aliases reaching a denied resolved IP through the Node TCPWrap / options-host path. URL strings, node:http2, undici, and IPv6 numeric/mapped-address variants were not exhaustively tested by the reporter.
Not affected
- Programs that do not use
--deny-netat all (the bug is specifically about deny rules being bypassed; allow rules were always checked against the original string). - Native Deno networking APIs (
Deno.connect,Deno.connectTls,fetch, ...), these already re-checked permissions after resolution as of PR #33203. - URL-string callers such as
fetch("http://2130706433/")ornode:http.request("http://2130706433/"), the URL parser normalized the hostname to its dotted-quad form before the permission check ran. - Calls that do not provide
host/hostname(e.g. connecting by IP literal or by a name that the deny rule already matches verbatim).
Workarounds
If you cannot upgrade immediately, reduce exposure by:
- Preferring an
--allow-netallowlist over a--deny-netdenylist. An allowlist denies numeric aliases by default because they don't match the listed hostnames; only the destinations you've explicitly permitted can be reached. - Validating untrusted host input before passing it to
node:net.connect/node:http.request. Reject hostnames that are purely decimal integers (/^\d+$/) or begin with0x, as these are the alias forms exploited by the bypass. - Avoiding the Node options-host path for sensitive calls in favour of URL-string forms, which are normalized by the URL parser before the permission check.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 2.7.14"
},
"package": {
"ecosystem": "crates.io",
"name": "deno"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.8.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-49411"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": true,
"github_reviewed_at": "2026-06-16T19:09:46Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "## Summary\n\nDeno\u0027s network permission model is designed so that `--deny-net` rules apply to the **resolved IP address** of a destination, not just the literal string supplied by the caller. That means `--deny-net=127.0.0.1` (or `--deny-net=127.0.0.0/8`) is expected to block any attempt to reach loopback, regardless of how the hostname is spelled.\n\nOn affected versions, the Node.js compatibility TCP path checked the permission against the **original hostname string** before resolution and then did not re-check after resolution. A caller could therefore pass a numeric alias of an IP address (for example the decimal integer `2130706433` or the hex form `0x7f000001`, both of which resolve to `127.0.0.1`) and reach the denied destination through `node:net.connect` or `node:http.request`\u0027s `{ host, port }` options form.\n\nThe native `Deno.connect()`, `fetch()`, and URL-string variants of `node:http.request(\"http://...\")` were not affected, because they either re-checked permissions after resolution or normalized the hostname through the URL parser before checking.\n\n## Proof of concept\n\nRun on Deno `2.7.14`, with a local TCP listener on `127.0.0.1:\u003cPORT\u003e`:\n\n```js\nimport net from \"node:net\";\n\n// --allow-net + --deny-net=127.0.0.0/8\n// (or even --deny-net=127.0.0.1:\u003cPORT\u003e)\nnet.connect({ host: \"2130706433\", port: PORT }); // CONNECTED \u274c\nnet.connect({ host: \"0x7f000001\", port: PORT }); // CONNECTED \u274c\nnet.connect({ host: \"127.0.0.1\", port: PORT }); // denied \u2705\n```\n\nThe same primitive reached the loopback HTTP listener through `node:http` when the destination was passed as options rather than as a URL string:\n\n```js\nimport http from \"node:http\";\n\n// options-form host \u2014 bypasses the deny rule on affected versions\nhttp.request({ hostname: \"2130706433\", port: PORT, path: \"/\" }).end();\n\n// URL-string form \u2014 correctly denied (URL parser normalizes the host)\nhttp.request(`http://2130706433:${PORT}/`).end();\n```\n\nThe server-side log showed the bypassed requests arriving from `127.0.0.1` with the numeric alias preserved in the `Host` header.\n\n## Impact\n\nA program that intentionally allows broad outbound network access but uses `--deny-net` to carve out protected destinations, typically loopback, private/internal ranges, or cloud-instance metadata IPs, could be made to reach those denied destinations from less-trusted code (a dependency, plugin, or attacker-controlled input) that funnels through `node:net.connect({ host })` or `node:http.request({ hostname })`.\n\nThe CVSS vector reflects this as a local-attack-vector, permissions-required confidentiality impact: the attacker needs to be able to run code inside the Deno process, and the demonstrated primitive is \"reach an explicitly denied IP.\" It does not by itself exfiltrate data or execute code; the further impact depends on what the now-reachable endpoint exposes.\n\nThe confirmed scope is **IPv4 numeric hostname aliases** reaching a denied resolved IP through the Node TCPWrap / options-host path. URL strings, `node:http2`, `undici`, and IPv6 numeric/mapped-address variants were not exhaustively tested by the reporter.\n\n## Not affected\n\n- Programs that do not use `--deny-net` at all (the bug is specifically about deny rules being bypassed; allow rules were always checked against the original string).\n- Native Deno networking APIs (`Deno.connect`, `Deno.connectTls`, `fetch`, ...), these already re-checked permissions after resolution as of PR #33203.\n- URL-string callers such as `fetch(\"http://2130706433/\")` or `node:http.request(\"http://2130706433/\")`, the URL parser normalized the hostname to its dotted-quad form before the permission check ran.\n- Calls that do not provide `host`/`hostname` (e.g. connecting by IP literal or by a name that the deny rule already matches verbatim).\n\n## Workarounds\n\nIf you cannot upgrade immediately, reduce exposure by:\n\n- **Preferring an `--allow-net` allowlist over a `--deny-net` denylist.** An allowlist denies numeric aliases by default because they don\u0027t match the listed hostnames; only the destinations you\u0027ve explicitly permitted can be reached.\n- **Validating untrusted host input** before passing it to `node:net.connect` / `node:http.request`. Reject hostnames that are purely decimal integers (`/^\\d+$/`) or begin with `0x`, as these are the alias forms exploited by the bypass.\n- **Avoiding the Node options-host path for sensitive calls** in favour of URL-string forms, which are normalized by the URL parser before the permission check.",
"id": "GHSA-v8fw-85r8-5m23",
"modified": "2026-06-16T19:09:46Z",
"published": "2026-06-16T19:09:46Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/denoland/deno/security/advisories/GHSA-v8fw-85r8-5m23"
},
{
"type": "PACKAGE",
"url": "https://github.com/denoland/deno"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Deno: Node TCPWrap numeric hostname aliases bypass --deny-net resolved-IP deny checks"
}
GHSA-V8G2-Q7CG-QVG6
Vulnerability from github – Published: 2022-05-17 00:33 – Updated: 2025-04-20 03:45The daily mandb cleanup job in Man-db before 2.7.6.1-1 as packaged in Ubuntu and Debian allows local users with access to the man account to gain privileges via vectors involving insecure chown use.
{
"affected": [],
"aliases": [
"CVE-2015-1336"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-09-28T01:29:00Z",
"severity": "HIGH"
},
"details": "The daily mandb cleanup job in Man-db before 2.7.6.1-1 as packaged in Ubuntu and Debian allows local users with access to the man account to gain privileges via vectors involving insecure chown use.",
"id": "GHSA-v8g2-q7cg-qvg6",
"modified": "2025-04-20T03:45:55Z",
"published": "2022-05-17T00:33:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-1336"
},
{
"type": "WEB",
"url": "https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840357"
},
{
"type": "WEB",
"url": "https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1482786"
},
{
"type": "WEB",
"url": "https://security.gentoo.org/glsa/201707-12"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/140759/Man-db-2.6.7.1-Privilege-Escalation.html"
},
{
"type": "WEB",
"url": "http://people.canonical.com/~ubuntu-security/cve/2015/CVE-2015-1336.html"
},
{
"type": "WEB",
"url": "http://www.halfdog.net/Security/2015/MandbSymlinkLocalRootPrivilegeEscalation"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2015/12/14/11"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/79723"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-V8G9-FQW6-F57H
Vulnerability from github – Published: 2026-06-17 18:35 – Updated: 2026-06-17 18:35Vulnerability in the Oracle WebCenter Content product of Oracle Fusion Middleware (component: Content Server). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebCenter Content. Successful attacks of this vulnerability can result in takeover of Oracle WebCenter Content. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
{
"affected": [],
"aliases": [
"CVE-2026-46766"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-06-17T10:53:54Z",
"severity": "CRITICAL"
},
"details": "Vulnerability in the Oracle WebCenter Content product of Oracle Fusion Middleware (component: Content Server). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebCenter Content. Successful attacks of this vulnerability can result in takeover of Oracle WebCenter Content. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).",
"id": "GHSA-v8g9-fqw6-f57h",
"modified": "2026-06-17T18:35:26Z",
"published": "2026-06-17T18:35:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46766"
},
{
"type": "WEB",
"url": "https://www.oracle.com/security-alerts/cspujun2026.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-V8HV-9RJ5-373R
Vulnerability from github – Published: 2026-05-28 21:32 – Updated: 2026-05-28 21:32Vulnerability in the Oracle Internet Procurement Connector product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Internet Procurement Connector. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Internet Procurement Connector accessible data as well as unauthorized access to critical data or complete access to all Oracle Internet Procurement Connector accessible data. CVSS 3.1 Base Score 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).
{
"affected": [],
"aliases": [
"CVE-2026-46819"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-28T21:16:31Z",
"severity": "CRITICAL"
},
"details": "Vulnerability in the Oracle Internet Procurement Connector product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Internet Procurement Connector. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Internet Procurement Connector accessible data as well as unauthorized access to critical data or complete access to all Oracle Internet Procurement Connector accessible data. CVSS 3.1 Base Score 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).",
"id": "GHSA-v8hv-9rj5-373r",
"modified": "2026-05-28T21:32:05Z",
"published": "2026-05-28T21:32:05Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46819"
},
{
"type": "WEB",
"url": "https://www.oracle.com/security-alerts/cspumay2026.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-V8MR-J3FH-R2C7
Vulnerability from github – Published: 2022-05-17 02:35 – Updated: 2022-05-17 02:35In all Android releases from CAF using the Linux kernel, some interfaces were improperly exposed to QTEE applications.
{
"affected": [],
"aliases": [
"CVE-2015-9024"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-06-13T20:29:00Z",
"severity": "MODERATE"
},
"details": "In all Android releases from CAF using the Linux kernel, some interfaces were improperly exposed to QTEE applications.",
"id": "GHSA-v8mr-j3fh-r2c7",
"modified": "2022-05-17T02:35:20Z",
"published": "2022-05-17T02:35:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-9024"
},
{
"type": "WEB",
"url": "https://source.android.com/security/bulletin/2017-06-01"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/98874"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id/1038623"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-V8P8-QFXX-RG74
Vulnerability from github – Published: 2025-12-17 21:30 – Updated: 2025-12-18 21:31This issue was addressed with additional entitlement checks. This issue is fixed in iOS 26.2 and iPadOS 26.2, iOS 18.7.3 and iPadOS 18.7.3. An app may be able to access user-sensitive data.
{
"affected": [],
"aliases": [
"CVE-2025-46292"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-17T21:16:14Z",
"severity": "MODERATE"
},
"details": "This issue was addressed with additional entitlement checks. This issue is fixed in iOS 26.2 and iPadOS 26.2, iOS 18.7.3 and iPadOS 18.7.3. An app may be able to access user-sensitive data.",
"id": "GHSA-v8p8-qfxx-rg74",
"modified": "2025-12-18T21:31:37Z",
"published": "2025-12-17T21:30:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-46292"
},
{
"type": "WEB",
"url": "https://support.apple.com/en-us/125884"
},
{
"type": "WEB",
"url": "https://support.apple.com/en-us/125885"
}
],
"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-V8PR-JQPJ-QM7G
Vulnerability from github – Published: 2026-07-01 00:34 – Updated: 2026-07-01 03:35Insufficient policy enforcement in Payments in Google Chrome on Android prior to 150.0.7871.47 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)
{
"affected": [],
"aliases": [
"CVE-2026-13949"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-06-30T23:17:08Z",
"severity": "MODERATE"
},
"details": "Insufficient policy enforcement in Payments in Google Chrome on Android prior to 150.0.7871.47 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)",
"id": "GHSA-v8pr-jqpj-qm7g",
"modified": "2026-07-01T03:35:22Z",
"published": "2026-07-01T00:34:07Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-13949"
},
{
"type": "WEB",
"url": "https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html"
},
{
"type": "WEB",
"url": "https://issues.chromium.org/issues/513311569"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-V8QC-J9PX-44HW
Vulnerability from github – Published: 2026-03-04 21:32 – Updated: 2026-03-05 21:30Inappropriate implementation in CSS in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page. (Chromium security severity: High)
{
"affected": [],
"aliases": [
"CVE-2026-3541"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-03-04T20:16:21Z",
"severity": "HIGH"
},
"details": "Inappropriate implementation in CSS in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page. (Chromium security severity: High)",
"id": "GHSA-v8qc-j9px-44hw",
"modified": "2026-03-05T21:30:33Z",
"published": "2026-03-04T21:32:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-3541"
},
{
"type": "WEB",
"url": "https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop.html"
},
{
"type": "WEB",
"url": "https://issues.chromium.org/issues/484811719"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation MIT-1
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Mitigation MIT-46
Strategy: Separation of Privilege
- Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
- Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
CAPEC-19: Embedding Scripts within Scripts
An adversary leverages the capability to execute their own script by embedding it within other scripts that the target software is likely to execute due to programs' vulnerabilities that are brought on by allowing remote hosts to execute scripts.
CAPEC-441: Malicious Logic Insertion
An adversary installs or adds malicious logic (also known as malware) into a seemingly benign component of a fielded system. This logic is often hidden from the user of the system and works behind the scenes to achieve negative impacts. With the proliferation of mass digital storage and inexpensive multimedia devices, Bluetooth and 802.11 support, new attack vectors for spreading malware are emerging for things we once thought of as innocuous greeting cards, picture frames, or digital projectors. This pattern of attack focuses on systems already fielded and used in operation as opposed to systems and their components that are still under development and part of the supply chain.
CAPEC-478: Modification of Windows Service Configuration
An adversary exploits a weakness in access control to modify the execution parameters of a Windows service. The goal of this attack is to execute a malicious binary in place of an existing service.
CAPEC-479: Malicious Root Certificate
An adversary exploits a weakness in authorization and installs a new root certificate on a compromised system. Certificates are commonly used for establishing secure TLS/SSL communications within a web browser. When a user attempts to browse a website that presents a certificate that is not trusted an error message will be displayed to warn the user of the security risk. Depending on the security settings, the browser may not allow the user to establish a connection to the website. Adversaries have used this technique to avoid security warnings prompting users when compromised systems connect over HTTPS to adversary controlled web servers that spoof legitimate websites in order to collect login credentials.
CAPEC-502: Intent Spoof
An adversary, through a previously installed malicious application, issues an intent directed toward a specific trusted application's component in an attempt to achieve a variety of different objectives including modification of data, information disclosure, and data injection. Components that have been unintentionally exported and made public are subject to this type of an attack. If the component trusts the intent's action without verififcation, then the target application performs the functionality at the adversary's request, helping the adversary achieve the desired negative technical impact.
CAPEC-503: WebView Exposure
An adversary, through a malicious web page, accesses application specific functionality by leveraging interfaces registered through WebView's addJavascriptInterface API. Once an interface is registered to WebView through addJavascriptInterface, it becomes global and all pages loaded in the WebView can call this interface.
CAPEC-536: Data Injected During Configuration
An attacker with access to data files and processes on a victim's system injects malicious data into critical operational data during configuration or recalibration, causing the victim's system to perform in a suboptimal manner that benefits the adversary.
CAPEC-546: Incomplete Data Deletion in a Multi-Tenant Environment
An adversary obtains unauthorized information due to insecure or incomplete data deletion in a multi-tenant environment. If a cloud provider fails to completely delete storage and data from former cloud tenants' systems/resources, once these resources are allocated to new, potentially malicious tenants, the latter can probe the provided resources for sensitive information still there.
CAPEC-550: Install New Service
When an operating system starts, it also starts programs called services or daemons. Adversaries may install a new service which will be executed at startup (on a Windows system, by modifying the registry). The service name may be disguised by using a name from a related operating system or benign software. Services are usually run with elevated privileges.
CAPEC-551: Modify Existing Service
When an operating system starts, it also starts programs called services or daemons. Modifying existing services may break existing services or may enable services that are disabled/not commonly used.
CAPEC-552: Install Rootkit
An adversary exploits a weakness in authentication to install malware that alters the functionality and information provide by targeted operating system API calls. Often referred to as rootkits, it is often used to hide the presence of programs, files, network connections, services, drivers, and other system components.
CAPEC-556: Replace File Extension Handlers
When a file is opened, its file handler is checked to determine which program opens the file. File handlers are configuration properties of many operating systems. Applications can modify the file handler for a given file extension to call an arbitrary program when a file with the given extension is opened.
CAPEC-558: Replace Trusted Executable
An adversary exploits weaknesses in privilege management or access control to replace a trusted executable with a malicious version and enable the execution of malware when that trusted executable is called.
CAPEC-562: Modify Shared File
An adversary manipulates the files in a shared location by adding malicious programs, scripts, or exploit code to valid content. Once a user opens the shared content, the tainted content is executed.
CAPEC-563: Add Malicious File to Shared Webroot
An adversaries may add malicious content to a website through the open file share and then browse to that content with a web browser to cause the server to execute the content. The malicious content will typically run under the context and permissions of the web server process, often resulting in local system or administrative privileges depending on how the web server is configured.
CAPEC-564: Run Software at Logon
Operating system allows logon scripts to be run whenever a specific user or users logon to a system. If adversaries can access these scripts, they may insert additional code into the logon script. This code can allow them to maintain persistence or move laterally within an enclave because it is executed every time the affected user or users logon to a computer. Modifying logon scripts can effectively bypass workstation and enclave firewalls. Depending on the access configuration of the logon scripts, either local credentials or a remote administrative account may be necessary.
CAPEC-578: Disable Security Software
An adversary exploits a weakness in access control to disable security tools so that detection does not occur. This can take the form of killing processes, deleting registry keys so that tools do not start at run time, deleting log files, or other methods.