CVE-2014-3188: Google Chrome before 38.0.2125.101 and Chrome OS before 38.0.2125.101 do not properly handle the interaction of IPC and Google V8, which…
Noroxi assessment
Priority: Plan (action score 42/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: 6.7% (FIRST EPSS); higher than 94% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: chromium-browser (Red Hat:rhel_extras:6) 0:38.0.2125.101-2.el6_6; chromium-browser-debuginfo (Red Hat:rhel_extras:6) 0:38.0.2125.101-2.el6_6.
Add it to your regular patch cycle. Upgrade to chromium-browser (Red Hat:rhel_extras:6) 0:38.0.2125.101-2.el6_6; chromium-browser-debuginfo (Red Hat:rhel_extras:6) 0:38.0.2125.101-2.el6_6 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
Google Chrome before 38.0.2125.101 and Chrome OS before 38.0.2125.101 do not properly handle the interaction of IPC and Google V8, which allows remote attackers to execute arbitrary code via vectors involving JSON data, related to improper parsing of an escaped index by ParseJsonObject in json-parser.h.
- Published
- Oct 8, 2014
- Updated
- Jun 16, 2026
- EPSS
- 6.7% · 94th percentile
- CWE
- CWE-94
Report tools
Action score
42
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 6.7%
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 os | cpe:2.3:o:google:chrome_os | |
| chrome | cpe:2.3:a:google:chrome | |
| redhat | enterprise linux desktop supplementary | cpe:2.3:o:redhat:enterprise_linux_desktop_supplementary |
| redhat | enterprise linux server supplementary | cpe:2.3:o:redhat:enterprise_linux_server_supplementary |
| redhat | enterprise linux server supplementary eus | cpe:2.3:o:redhat:enterprise_linux_server_supplementary_eus |
| redhat | enterprise linux workstation supplementary | cpe:2.3:o:redhat:enterprise_linux_workstation_supplementary |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- google chromeup to 38.0.2125.7 inclusive
- google chrome osup to 38.0.2125.77 inclusive
- redhat enterprise linux desktop supplementary6.0
- redhat enterprise linux server supplementary6.0
- redhat enterprise linux server supplementary eus6.6.z
- redhat enterprise linux workstation supplementary6.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:rhel_extras:6 | chromium-browser | before 0:38.0.2125.101-2.el6_6 | 0:38.0.2125.101-2.el6_6 |
| Red Hat:rhel_extras:6 | chromium-browser-debuginfo | before 0:38.0.2125.101-2.el6_6 | 0:38.0.2125.101-2.el6_6 |
Same product
google: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-1708The boot implementation in Google Chrome OS before 33.0.1750.152 does not properly consider file persistence, which allows remote attackers…41Plan
- CVE-2012-2864Mesa, as used in Google Chrome before 21.0.1183.0 on the Acer AC700, Cr-48, and Samsung Series 5 and 5 550 Chromebook platforms, and the…41Plan
- CVE-2011-0485Google Chrome before 8.0.552.237 and Chrome OS before 8.0.552.344 do not properly handle speech data, which allows remote attackers to…41Plan
Published before and after this one in the same product
- ← EarlierCVE-2014-1710Mar 16, 2014 · The AsyncPixelTransfersCompletedQuery::End function in gpu/command_buffer/service/query_manager.cc in Google Chrome, as used in Google…30Monitor
- ← EarlierCVE-2014-1711Mar 16, 2014 · The GPU driver in the kernel in Google Chrome OS before 33.0.1750.152 allows remote attackers to cause a denial of service (out-of-bounds…30Monitor
- Later →CVE-2016-5169Sep 25, 2016 · Format string vulnerability in Google Chrome OS before 53.0.2785.103 allows remote attackers to cause a denial of service or possibly have…35Monitor
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 |
|---|---|---|
| red hat:chromium-browser | 0:38.0.2125.101-2.el6_6 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| red hat:chromium-browser-debuginfo | 0:38.0.2125.101-2.el6_6 · Red Hat:rhel_extras:6 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
AV:N/AC:L/Au:N/C:C/I:C/A:C
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)
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.