CVE-2017-14937

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. High risk of data exposure.

Exploit odds

1.0% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2017-10-20 14:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 01:07 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.0% in the next 30 days (EPSS).
• Severity: 4.7 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2017-10-20 14:29 UTC

Last modified

2026-06-17 01:07 UTC

Exploit probability

1.0% · EPSS, next 30 days

Weakness

CWE-327 · Broken cryptographic algorithm

Record status

Modified

Affected

• Pcu 2014

Attack profile CVSS 3.0 · 4.7

Attack vector

Local

Complexity

High

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2017-14937.md and follow it. Check whether this project is affected by CVE-2017-14937. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge