Skip to main content
VulnerabilityPublished Updated

CVE-2023-46047: backends · Improper Input Validation

Affects backendsSource CVE Database V5

0

Not known to be exploited · CVSS 7.3 High.

Data as of 26 Oct 2026, 09:15 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Mar 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
GitHubsane-project/backendspkg:github/sane-project/backendsOther threatsAffected
  • =1.2.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2023-46047 effectively, European organizations should implement several specific measures beyond generic advice: 1) Restrict local file system permissions to prevent unauthorized users from writing or modifying configuration files used by Sane, ensuring only trusted administrators have such access. 2) Employ file integrity monitoring solutions to detect unauthorized changes to configuration files related to the scanning software. 3) Limit the number of users with local access to systems running Sane, enforcing strict access controls and user account management policies. 4) Use application whitelisting or sandboxing techniques to restrict the execution of unauthorized code that could be triggered by malicious configuration files. 5) Monitor logs and system behavior for anomalies related to scanning software execution or configuration changes. 6) Stay informed about vendor or community updates regarding patches or security advisories for Sane and apply them promptly once available. 7) Educate users about the risks of local file manipulation and enforce policies to prevent the introduction of untrusted files into scanning environments. These targeted actions will reduce the attack surface and limit the potential for exploitation until an official patch is released.

Description

An issue in Sane 1.2.1 allows a local attacker to execute arbitrary code via a crafted file to the sanei_configure_attach() function. NOTE: this is disputed because there is no expectation that the product should be starting with an attacker-controlled configuration file.

References

Community reviews

Loading reviews…