Enterprise Linux Desktop SupplementaryOperating system · Redhat
CVE-2014-3193
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 SessionService::GetLastSession function in browser/sessions/session_service.cc in Google Chrome before 38.0.2125.101 allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via vectors that leverage "type confusion" for callback processing.
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 confidenceA type confusion vulnerability in Chrome's SessionService::GetLastSession function allows remote attackers to trigger a use-after-free condition by manipulating callback processing, potentially leading to denial of service or unspecified other impact.
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
Enterprise Linux Desktop SupplementaryOperating system
= 6.0
Enterprise Linux Server SupplementaryOperating system
= 6.0
Enterprise Linux Server Supplementary EusOperating system
= 6.6.z
Enterprise Linux Workstation SupplementaryOperating system
= 6.0
ChromeWeb browser
<= 38.0.2125.7CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 if Google Chrome is installedOn Linux: rpm -q google-chrome-stable or dpkg -l | grep chrome. On Windows: Check for Chrome in Program Files or run 'chrome --version' from Command Prompt. On macOS: check /Applications folder or run '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version'Affected if Google Chrome browser is present on the system
-
Determine the installed Chrome versionRun 'google-chrome --version' or 'google-chrome-stable --version' in terminal. On Windows, open Chrome and go to Help > About Google Chrome, or run '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' in Command PromptAffected if Version returned is blank or cannot be determined (Chrome may be installed but version detection fails)
-
Compare installed version against affected rangeCompare the detected version number to 38.0.2125.7. The affected range is any version less than or equal to 38.0.2125.7Affected if Installed version is 38.0.2125.7 or earlier (e.g., 38.0.2125.0 through 38.0.2125.7, or any 37.x/36.x version)
-
Verify SessionService feature is in useThis vulnerability is triggered through the SessionService API during session restore operations. The flaw is present in the underlying Chrome binary and does not require specific user configuration to be exploitableAffected if Chrome is running and the installed version is within the affected range
If Google Chrome version 38.0.2125.7 or earlier is installed, the system is affected by this vulnerability.
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 38.0.2125.101 or later to remediate this vulnerability.
Fix this in Enterprise Linux Desktop Supplementary
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3193 — 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-3193 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