Physical boot of modified kernel via authenticity bypass
Published Jun 15, 2021 · Updated Aug 4, 2024
Insufficient verification of data authenticity in Peloton TTR01 through PTV55G allows attackers with physical access to boot modified kernel/ramdisk. The boot process accepts a modified kernel or ramdisk without authenticating the bootloader state. Physical access is required, and the attacker can alter confidentiality, integrity, and availability by running modified firmware.
Summary
What happened
Insufficient verification of data authenticity in Peloton TTR01 through PTV55G allows attackers with physical access to boot modified kernel/ramdisk. The boot process accepts a modified kernel or ramdisk without authenticating the bootloader state. Physical access is required, and the attacker can alter confidentiality, integrity, and availability by running modified firmware.
The record
- CVE
- CVE-2021-33887
- Published
- Jun 15, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-345, T1601.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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
- Peloton TTR01 modified-kernel boot demonstrationproof of concept · demonstrated
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