Credential disclosure via cleartext flash storage
Published Dec 26, 2022 · Updated Apr 11, 2025
Cleartext credential storage in General Electric iNET and iNET II before 8.3.0 allows physically proximate attackers to read credentials. The firmware stores credentials in onboard flash memory without encryption, leaving their values recoverable from the device's nonvolatile storage. Physical access to the radio is required, and the reported consequence is limited to disclosure of the stored credentials.
Summary
What happened
Cleartext credential storage in General Electric iNET and iNET II before 8.3.0 allows physically proximate attackers to read credentials. The firmware stores credentials in onboard flash memory without encryption, leaving their values recoverable from the device's nonvolatile storage. Physical access to the radio is required, and the reported consequence is limited to disclosure of the stored credentials.
The record
- CVE
- CVE-2022-24120
- Published
- Dec 26, 2022
- Updated
- Apr 11, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-312, CAPEC-37, T1552
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 26, 2022CVE publishedPublication date reported by the CVE source.
- Apr 11, 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