CVE-2024-28146: Image Access Scan2Net · Use of Hard-coded Credentials
Affects Image Access Scan2NetSource CVE Database V5
Not known to be exploited · CVSS 8.4 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Image Access GmbH Scan2Net | Affected
| Fixed in– |
AI-suggested
Immediate mitigation steps include isolating Scan2Net devices from untrusted networks to limit local access opportunities. Organizations should monitor network traffic for unusual database connection attempts and unauthorized firmware update activities. Since no patches are currently available, administrators should enforce strict access controls around devices, including network segmentation and limiting physical access. Implementing application-layer firewalls or intrusion detection systems to detect anomalous behavior related to backup encryption or firmware decryption processes can help. Vendors and users should prioritize the development and deployment of firmware updates that remove hard-coded credentials and replace them with secure credential management solutions such as hardware security modules or secure vaults. Additionally, organizations should conduct thorough audits of device configurations and logs to detect any signs of compromise. Training staff to recognize and respond to suspicious device behavior is also recommended.
Description
The application uses several hard-coded credentials to encrypt config files during backup, to decrypt the new firmware during an update and some passwords allow a direct connection to the database server of the affected device.