Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2003-0775: saned in sane-backends 1.0.7 and earlier calls malloc with an arbitrary size value if a connection is dropped

43
This month
MEDIUM 5.0DOWNGRADEDOWNGRADE

CVE-2003-0775 is a medium-severity flaw (CVSS 5.0) affecting sane, sane-backend. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

saned in sane-backends 1.0.7 and earlier calls malloc with an arbitrary size value if a connection is dropped before the size value has been sent, which allows remote attackers to cause a denial of service (memory consumption or crash).

Why this priority

  • Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score5.0 (Medium)
EPSS exploit chance2.1% (top 18%)
CISA exploited listNo
Published2003-09-22
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: sane

Share: LinkedIn · X · Reddit

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

sane sane DOWNGRADE
Affected: 1.0.0 · 1.0.1 · 1.0.2 · 1.0.3 · 1.0.4 · 1.0.5 · 1.0.6 · 1.0.7
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0.0
1. Check installed version
apt-cache policy sane || rpm -q sane || sane --version
2. No fixed release: DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)
apt-cache madison sane sudo apt install sane=<VERSION_BEFORE_1.0.0> sudo apt-mark hold sane
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list sane sudo dnf downgrade sane-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add sane
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
sane sane-backend DOWNGRADE
Affected: 1.0.10
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0.10
1. Check installed version
apt-cache policy sane-backend || rpm -q sane-backend || sane-backend --version
2. No fixed release: DOWNGRADE to a release before 1.0.10 (Debian / Ubuntu)
apt-cache madison sane-backend sudo apt install sane-backend=<VERSION_BEFORE_1.0.10> sudo apt-mark hold sane-backend
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list sane-backend sudo dnf downgrade sane-backend-<VERSION_BEFORE_1.0.10> sudo dnf versionlock add sane-backend
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2003-0775?

sane: downgrade or apply the listed mitigation; sane-backend: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2003-0775 being exploited?

CVE-2003-0775 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2003-0775 affect?

CVE-2003-0775 affects sane, sane-backend. Severity is medium (CVSS 5.0). saned in sane-backends 1.0.7 and earlier calls malloc with an arbitrary size value if a connection is dropped before the size value has been sent, which allows remote attackers to cause a denial of service (memory consumption or crash).

How urgent is CVE-2003-0775?

Priority 43/100. Public exploit reference

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.