False aircraft injection via spoofed RF signals
Published Jan 22, 2025 · Updated Feb 12, 2025
Input validation failure in TCAS II 7.1 and earlier allows physically proximate attackers to inject false aircraft tracks via spoofed RF signals. The traffic-processing path accepts attacker-generated location data carried in crafted radio transmissions and uses it to populate collision tracks. Exploitation requires software-defined radio hardware, a custom low-latency pipeline, and specific laboratory conditions; successful injection creates phantom traffic and can trigger unwanted resolution advisories.
Summary
What happened
Input validation failure in TCAS II 7.1 and earlier allows physically proximate attackers to inject false aircraft tracks via spoofed RF signals. The traffic-processing path accepts attacker-generated location data carried in crafted radio transmissions and uses it to populate collision tracks. Exploitation requires software-defined radio hardware, a custom low-latency pipeline, and specific laboratory conditions; successful injection creates phantom traffic and can trigger unwanted resolution advisories.
The record
- CVE
- CVE-2024-9310
- Published
- Jan 22, 2025
- Updated
- Feb 12, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-807, T0831
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 22, 2025CVE publishedPublication date reported by the CVE source.
- Feb 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo