dbcve.org
S Gold 2 Pmb 8876Hardware / appliance · Infineon

CVE-2017-9633

HIGH · 8.8 CVSS v3.1 Published 2017-08-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
An Improper Restriction of Operations within the Bounds of a Memory Buffer issue was discovered in the Continental AG Infineon S-Gold 2 (PMB 8876) chipset on BMW several models produced between 2009-2010, Ford a limited number of P-HEV vehicles, Infiniti 2013 JX35, Infiniti 2014-2016 QX60, Infiniti 2014-2016 QX60 Hybrid, Infiniti 2014-2015 QX50, Infiniti 2014-2015 QX50 Hybrid, Infiniti 2013 M37/M56, Infiniti 2014-2016 Q70, Infiniti 2014-2016 Q70L, Infiniti 2015-2016 Q70 Hybrid, Infiniti 2013 QX56, Infiniti 2014-2016 QX 80, and Nissan 2011-2015 Leaf. A vulnerability in the temporary mobile subscriber identity (TMSI) may allow an attacker to access and control memory. This may allow remote code execution on the baseband radio processor of the TCU.

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 · moderate confidence

A buffer overflow vulnerability exists in the TMSI (Temporary Mobile Subscriber Identity) handling of the Infineon S-Gold 2 (PMB 8876) chipset used in telematics control units (TCU). The improper memory buffer restriction allows an attacker to overflow allocated memory boundaries, enabling memory manipulation and potentially achieving remote code execution on the baseband radio processor.

MitigationApply firmware updates provided by the chipset vendor (Infineon/Continental) through automotive OEM channels; until patches are available, implement network-level controls to restrict unauthorized access to the TCU's cellular interface.

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
S Gold 2 Pmb 8876Hardware / appliance
Affected:all versions

CVSS 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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the cellular chipset model
    Examine the device hardware specifications, baseband firmware strings, or boot logs for 'PMB 8876' or 'S-Gold 2' identifiers. This may require access to the TCU's diagnostic interface or baseband processor debug output.
    Affected if The chipset is Infineon PMB 8876 (S-Gold 2)
  2. Confirm the device is a telematics control unit
    Verify the device is a TCU with cellular connectivity by checking the hardware model number, product documentation, or cellular module identification in the system.
    Affected if The device is a telematics control unit using the Infineon S-Gold 2 chipset
  3. Check baseband firmware version
    Retrieve the baseband radio processor firmware version through AT commands (e.g., AT+CGMR), diagnostic logs, or firmware extraction if accessible.
    Affected if Any firmware version is present on the S-Gold 2 PMB 8876 chipset (all versions are affected)
  4. Verify TMSI processing is active
    Monitor cellular network signaling logs or use AT commands to confirm the device performs TMSI (Temporary Mobile Subscriber Identity) Attach procedures on the mobile network.
    Affected if The device performs TMSI handling on the cellular network (standard in all GSM/UMTS TCU operation)

The environment is affected if any telematics control unit or cellular device utilizes the Infineon S-Gold 2 (PMB 8876) chipset, as all firmware versions contain the vulnerability in TMSI handling.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply firmware updates provided by the chipset vendor (Infineon/Continental) through automotive OEM channels; until patches are available, implement network-level controls to restrict unauthorized access to the TCU's cellular interface.

Fix this in S Gold 2 Pmb 8876 Scoped from the published advisory
  • Consultation40.0 h
  • Implementation80.0 h
  • Testing60.0 h
  • Review / QA30.0 h
210.0 hours of engineering $36,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $58,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-9633 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-9633 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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