Skip to main content
VulnerabilityPublished Updated

CVE-2024-28140: Image Access Scan2Net · Execution with Unnecessary Privileges

Affects Image Access Scan2NetSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Image Access GmbH Scan2NetAffected
  • =0
Fixed in–

AI-suggested

To mitigate CVE-2024-28140, organizations should implement the following specific measures: 1) Immediately audit all Scan2Net devices to verify the privilege levels of running applications and confirm if the kiosk browser runs as root. 2) Where possible, reconfigure or harden the device to run the browser and other applications with least privilege, avoiding root execution. 3) Isolate Scan2Net devices on dedicated network segments or VLANs with strict access controls to limit exposure to untrusted networks or users. 4) Monitor network traffic and device logs for unusual activity indicative of exploitation attempts. 5) Engage with Image Access GmbH to obtain timelines for patches or firmware updates addressing this vulnerability and apply them promptly once available. 6) Consider deploying host-based intrusion detection or endpoint protection solutions on devices if supported. 7) Educate staff about the risks of connecting scanning devices to unsecured networks. 8) If device reconfiguration is not feasible, consider replacing affected devices with more secure alternatives. These steps go beyond generic advice by focusing on privilege reduction, network isolation, and proactive vendor engagement.

Description

The scanner device boots into a kiosk mode by default and opens the Scan2Net interface in a browser window. This browser is run with the permissions of the root user. There are also several other applications running as root user. This can be confirmed by running "ps aux" as the root user and observing the output.

References

Community reviews

Loading reviews…