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

CVE-2017-9647

MEDIUM · 6.6 CVSS v3.0 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 →
68/100
Remediation priority · Elevated
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
A Stack-Based Buffer Overflow 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. An attacker with a physical connection to the TCU may exploit a buffer overflow condition that exists in the processing of AT commands. This may allow arbitrary 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 · high confidence

A stack-based buffer overflow vulnerability exists in the Continental AG Infineon S-Gold 2 (PMB 8876) chipset used in vehicle Telematics Control Units (TCUs). The flaw is in the processing of AT commands and can be exploited via physical connection to the TCU, potentially allowing arbitrary code execution on the baseband radio processor.

MitigationPrimary mitigation involves restricting physical access to TCU components; definitive remediation requires vendor-supplied firmware updates from Continental AG/Infineon to patch the AT command parser. Vehicle-level software updates or hardware replacement may be necessary.

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

CVSS:3.0/AV:P/AC:L/PR:L/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 TCU chipset model
    Locate the Telematics Control Unit (TCU) in the vehicle or device and inspect the chipset markings. Look for 'Infineon S-Gold 2' or 'PMB 8876' on the processor chip.
    Affected if The TCU contains an Infineon S-Gold 2 PMB 8876 chipset
  2. Determine if AT command interface is active
    Connect to the TCU via debug ports (UART, JTAG, or USB diagnostic interfaces) and attempt to send AT commands. Check if the baseband radio processor responds to AT command queries.
    Affected if AT command processing is enabled and the TCU responds to AT commands via physical interface
  3. Verify physical access controls to TCU
    Inspect the physical security of the TCU enclosure. Determine if the diagnostic ports (OBD-II, USB, debug headers) are exposed or accessible without authorization.
    Affected if Physical access to TCU debug ports is unrestricted or uncontrolled
  4. Check firmware version if accessible
    If firmware can be extracted or queried via diagnostic tools, document the firmware version. Compare against any vendor-released patched versions for the S-Gold 2 chipset.
    Affected if The firmware is an unpatched version and no vendor security update has been applied to the TCU

The environment is affected if a Telematics Control Unit containing the Infineon S-Gold 2 PMB 8876 chipset is present with AT command interface enabled and accessible, as exploitation requires physical access to send malicious AT commands to trigger the buffer overflow.

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

Primary mitigation involves restricting physical access to TCU components; definitive remediation requires vendor-supplied firmware updates from Continental AG/Infineon to patch the AT command parser. Vehicle-level software updates or hardware replacement may be necessary.

Fix this in S Gold 2 Pmb 8876 Scoped from the published advisory
  • Consultation25.0 h
  • Implementation50.0 h
  • Testing35.0 h
  • Review / QA20.0 h
130.0 hours of engineering $22,850
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-9647 — 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-9647 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