CVE-2017-15396: A stack buffer overflow in NumberingSystem in International Components for Unicode (ICU) for C/C++ before 60.2, as used in V8 in Google…
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.2% (FIRST EPSS); higher than 82.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-browser (Debian:9) 62.0.3202.75-1~deb9u1; chromium (openSUSE:Tumbleweed) 93.0.4577.82-1.1; chromium-browser (Red Hat:rhel_extras:6) 0:62.0.3202.75-1.el6_9.
Low priority for now. Upgrade to chromium-browser (Debian:9) 62.0.3202.75-1~deb9u1; chromium (openSUSE:Tumbleweed) 93.0.4577.82-1.1; chromium-browser (Red Hat:rhel_extras:6) 0:62.0.3202.75-1.el6_9 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
A stack buffer overflow in NumberingSystem in International Components for Unicode (ICU) for C/C++ before 60.2, as used in V8 in Google Chrome prior to 62.0.3202.75 and other products, allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
- Published
- Aug 28, 2018
- Updated
- Jun 16, 2026
- EPSS
- 2.2% · 82th percentile
- CWE
- CWE-119
Report tools
Action score
27
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 | |
| redhat | enterprise linux desktop | cpe:2.3:o:redhat:enterprise_linux_desktop |
| redhat | enterprise linux server | cpe:2.3:o:redhat:enterprise_linux_server |
| redhat | enterprise linux workstation | cpe:2.3:o:redhat:enterprise_linux_workstation |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| icu-project | international components for unicode | cpe:2.3:a:icu-project:international_components_for_unicode |
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.
n/a Google Chrome prior to 62.0.3202.75 unknown
- Google Chrome prior to 62.0.3202.75 unknownaffected
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- debian debian linux8.0
- debian debian linux9.0
- google chromebefore 62.0.3202.75
- icu-project international components for unicodebefore 60.2
- redhat enterprise linux desktop6.0
- redhat enterprise linux server6.0
- redhat enterprise linux workstation6.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:9 | chromium-browser | before 62.0.3202.75-1~deb9u1 | 62.0.3202.75-1~deb9u1 |
| openSUSE:Tumbleweed | chromium | before 93.0.4577.82-1.1 | 93.0.4577.82-1.1 |
| Red Hat:rhel_extras:6 | chromium-browser | before 0:62.0.3202.75-1.el6_9 | 0:62.0.3202.75-1.el6_9 |
| Red Hat:rhel_extras:6 | chromium-browser-debuginfo | before 0:62.0.3202.75-1.el6_9 | 0:62.0.3202.75-1.el6_9 |
| SUSE:Package Hub 12 SP2 | chromium | before 63.0.3239.84-40.1 | 63.0.3239.84-40.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…KEV95Now
- 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…KEV90Now
- 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…KEV90Now
Published before and after this one in the same product
- ← EarlierCVE-2017-15427Aug 28, 2018 · Insufficient policy enforcement in Omnibox in Google Chrome prior to 63.0.3239.84 allowed a socially engineered user to XSS themselves by…24Monitor
- ← EarlierCVE-2017-15430Aug 28, 2018 · Insufficient data validation in Chromecast plugin in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to inject arbitrary…17Monitor
- Later →CVE-2017-15398Aug 28, 2018 · A stack buffer overflow in the QUIC networking stack in Google Chrome prior to 62.0.3202.89 allowed a remote attacker to gain code…40Plan
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-browser | 62.0.3202.75-1~deb9u1 · Debian:9 | Package registry (OSV) |
| opensuse:chromium | 93.0.4577.82-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:chromium-browser | 0:62.0.3202.75-1.el6_9 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| red hat:chromium-browser-debuginfo | 0:62.0.3202.75-1.el6_9 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| suse:chromium | 63.0.3239.84-40.1 · SUSE:Package Hub 12 SP2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.