CVE & CISA-KEV Catalog

CVE-2017-14937

MEDIUM
4.7
CVSS v3
NVD

Description

The airbag detonation algorithm allows injury to passenger-car occupants via predictable Security Access (SA) data to the internal CAN bus (or the OBD connector). This affects the airbag control units (aka pyrotechnical control units or PCUs) of unspecified passenger vehicles manufactured in 2014 or later, when the ignition is on and the speed is less than 6 km/h. Specifically, there are only 256 possible key pairs, and authentication attempts have no rate limit. In addition, at least one manufacturer's interpretation of the ISO 26021 standard is that it must be possible to calculate the key directly (i.e., the other 255 key pairs must not be used). Exploitation would typically involve an attacker who has already gained access to the CAN bus, and sends a crafted Unified Diagnostic Service (UDS) message to detonate the pyrotechnical charges, resulting in the same passenger-injury risks as in any airbag deployment.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorLocal
Attack ComplexityHigh
Privileges RequiredLow
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityNone
AvailabilityNone

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

Exploit Intelligence

0.99%probability of exploitation in 30 days
59thpercentile

Moderate risk: more likely to be exploited than 59% of all known CVEs.

References

Third-Party Advisory1

Related Vulnerabilities

Other CWE-327 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2015-2808Low3.774%-Fix
CVE-2023-34039Critical9.864%-Fix
CVE-2016-6602Critical9.855%--
CVE-2014-8687Critical9.844%--
CVE-2020-13777High7.418%-Fix
CVE-2017-17428Medium5.915%--

Common questions

How do I fix CVE-2017-14937?

No published fix for CVE-2017-14937 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2017-14937 being actively exploited?

Not that we know of. CVE-2017-14937 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.99% is the estimated probability that it will be exploited in the next 30 days. That is higher than 59% of all scored CVEs.

How severe is CVE-2017-14937?

CVE-2017-14937 has a CVSS v3 base score of 4.7, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2017-14937
CVE-2017-14937 severity badge

Markdown

[![CVE-2017-14937](https://tridentstack.com/cve/badge/CVE-2017-14937.svg)](https://tridentstack.com/cve/CVE-2017-14937)

HTML

<a href="https://tridentstack.com/cve/CVE-2017-14937"><img src="https://tridentstack.com/cve/badge/CVE-2017-14937.svg" alt="CVE-2017-14937"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-05-13.