ChromeWeb browser · Google
CVE-2014-1746
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe InMemoryUrlProtocol::Read function in media/filters/in_memory_url_protocol.cc in Google Chrome before 35.0.1916.114 relies on an insufficiently large integer data type, which allows remote attackers to cause a denial of service (out-of-bounds read) via vectors that trigger use of a large buffer.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceInMemoryUrlProtocol::Read in Chrome's media/filters/in_memory_url_protocol.cc uses an integer data type too small to handle large buffer sizes, causing an out-of-bounds read when processing large buffers and resulting in a denial of service condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
<= 35.0.1916.113= 35.0.1916.0= 35.0.1916.1= 35.0.1916.2= 35.0.1916.3= 35.0.1916.4= 35.0.1916.5= 35.0.1916.6= 35.0.1916.7= 35.0.1916.8= 35.0.1916.9= 35.0.1916.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Chrome browser versionNavigate to chrome://settings/help or use the Help > About Google Chrome menu to view the installed version numberAffected if The displayed version is 35.0.1916.113 or earlier (including any version from 35.0.1916.0 through 35.0.1916.113)
-
Verify media filter component presenceThe vulnerable InMemoryUrlProtocol::Read function resides in Chrome's media/filters/in_memory_url_protocol.cc. This is a built-in media component present in all Chrome installations with media playback capabilities. No separate module check is required as this code is compiled into the browser binary.Affected if The media filter component exists in the installation (always true for standard Chrome builds with media support)
-
Confirm the vulnerability trigger conditionThe flaw triggers when processing large buffers through the InMemoryUrlProtocol::Read function. This occurs when loading media files that use in-memory URL protocol handling.Affected if The browser processes large media buffers while the vulnerable code version is in use
If your Chrome version is 35.0.1916.113 or earlier (specifically any version from 35.0.1916.0 through 35.0.1916.113), your environment contains the vulnerable integer type in InMemoryUrlProtocol::Read and is affected.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Google Chrome to version 35.0.1916.114 or later, which contains the fix for the insufficient integer type issue in the InMemoryUrlProtocol::Read function.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1746 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-1746 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data