CVE-2023-4357: Insufficient validation of untrusted input in XML in Google Chrome prior to 116.0.5845.96 allowed a remote attacker to bypass file access re
Noroxi assessment
Priority: Plan (action score 49/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 47.1% (FIRST EPSS); higher than 98.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: chromium (Debian:11) 116.0.5845.96-1~deb11u1; chromium (Debian:12) 116.0.5845.96-1~deb12u1; chromium (Debian:13) 116.0.5845.96-1.
Add it to your regular patch cycle. Upgrade to chromium (Debian:11) 116.0.5845.96-1~deb11u1; chromium (Debian:12) 116.0.5845.96-1~deb12u1; chromium (Debian:13) 116.0.5845.96-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Insufficient validation of untrusted input in XML in Google Chrome prior to 116.0.5845.96 allowed a remote attacker to bypass file access restrictions via a crafted HTML page. (Chromium security severity: Medium)
- Published
- Aug 15, 2023
- Updated
- Jun 17, 2026
- EPSS
- 47.1% · 98th percentile
- CWE
- CWE-20
Report tools
Action score
49
Plan
Add it to your regular patch cycle.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 14 / 30 · 47.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| chrome | cpe:2.3:a:google:chrome | |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- debian debian linux12.0
- fedoraproject fedora38
- google chromebefore 116.0.5845.96
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Chrome). Independent of NVD's CPE analysis and usually ahead of it.
Google Chrome
- 116.0.5845.96 and later · before 116.0.5845.96affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | chromium | before 116.0.5845.96-1~deb11u1 | 116.0.5845.96-1~deb11u1 |
| Debian:12 | chromium | before 116.0.5845.96-1~deb12u1 | 116.0.5845.96-1~deb12u1 |
| Debian:13 | chromium | before 116.0.5845.96-1 | 116.0.5845.96-1 |
| openSUSE:Leap 15.4 | chromium | before 116.0.5845.96-bp155.2.19.1 | 116.0.5845.96-bp155.2.19.1 |
| openSUSE:Tumbleweed | chromium | before 116.0.5845.96-1.1 | 116.0.5845.96-1.1 |
| SUSE:Package Hub 15 SP4 | chromium | before 116.0.5845.96-bp155.2.19.1 | 116.0.5845.96-bp155.2.19.1 |
Same product
google: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4863Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of boKEV95Now
- CVE-2021-21224Type confusion in V8 in Google Chrome prior to 90.0.4430.85 allowed a remote attacker to execute arbitrary code inside a sandbox via a craftKEV90Now
- CVE-2018-17463Incorrect side effect annotation in V8 in Google Chrome prior to 70.0.3538.64 allowed a remote attacker to execute arbitrary code inside a sKEV90Now
Published before and after this one in the same product
- ← EarlierCVE-2023-4355Aug 15, 2023 · Out of bounds memory access in V8 in Google Chrome prior to 116.0.5845.96 allowed a remote attacker to potentially exploit heap corruption v43Plan
- ← EarlierCVE-2023-4356Aug 15, 2023 · Use after free in Audio in Google Chrome prior to 116.0.5845.96 allowed a remote attacker who has convinced a user to engage in specific UI 35Monitor
- Later →CVE-2023-4358Aug 15, 2023 · Use after free in DNS in Google Chrome prior to 116.0.5845.96 allowed a remote attacker to potentially exploit heap corruption via a crafted35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:chromium | 116.0.5845.96-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:chromium | 116.0.5845.96-bp155.2.19.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| suse:chromium | 116.0.5845.96-bp155.2.19.1 · SUSE:Package Hub 15 SP4 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×7
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:229 | 2023-11-17 |
| Proof-of-concept repository on GitHub | stars:0 | 2023-11-21 |
| Proof-of-concept repository on GitHub | stars:4 | 2023-11-29 |
| Proof-of-concept repository on GitHub | stars:0 | 2024-01-09 |
| Proof-of-concept repository on GitHub | stars:4 | 2024-03-17 |
| Proof-of-concept repository on GitHub | stars:0 | 2024-06-20 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-02 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+93 d
- TodayOct 29, 2026+1171 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- crbug.com/1458911
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2DMXHPRUGBUDNHZCZCIVMWAUIEXEGMGT/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OCFEK63FUHFXZH5MSG6TNQOXMQWM4M5S/
- security.gentoo.org/glsa/202401-34
- www.debian.org/security/2023/dsa-5479
Vendor advisories and official records. Exploit/PoC links are deliberately left out.