PWC chip control via hard-coded console password
Published Dec 1, 2023 · Updated Dec 2, 2024
Use of a hard-coded password in JOYNEXT MIB3 firmware 0304 and earlier allows physically proximate attackers to control the PWC chip. The firmware embeds a fixed credential for the PoWer Controller debugging console, allowing the credential to replace unique per-unit authentication. Physical access to the infotainment unit is required, after which console commands provide full control of the PWC chip and can alter or interrupt its operation.
Summary
What happened
Use of a hard-coded password in JOYNEXT MIB3 firmware 0304 and earlier allows physically proximate attackers to control the PWC chip. The firmware embeds a fixed credential for the PoWer Controller debugging console, allowing the credential to replace unique per-unit authentication. Physical access to the infotainment unit is required, after which console commands provide full control of the PWC chip and can alter or interrupt its operation.
The record
- CVE
- CVE-2023-28895
- Published
- Dec 1, 2023
- Updated
- Dec 2, 2024
- Vendor
- JOYNEXT GmbH
- Product
- JOYNEXT MIB3 Infotainment Unit
- Classifications
- CWE-798, CWE-259, CAPEC-37
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 1, 2023CVE publishedPublication date reported by the CVE source.
- Dec 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0304
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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