Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-6318: saned in sane-backends 1.0.25 allows remote attackers to obtain sensitive memory information via a crafted SAN

53
This month
HIGH 7.5REMOTEMITIGATEDOWNGRADE

CVE-2017-6318 is a high-severity flaw (CVSS 7.5) affecting leap, sane-backends. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

saned in sane-backends 1.0.25 allows remote attackers to obtain sensitive memory information via a crafted SANE_NET_CONTROL_OPTION packet.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

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

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance3.0% (top 13%)
CISA exploited listNo
WeaknessCWE-200
Published2017-03-20
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: opensuse · sane-backends project

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

opensuse leap MITIGATE
Affected: 42.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 42.1
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
sane-backends project sane-backends DOWNGRADE
Affected: 1.0.25
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0.25
1. Check installed version
apt-cache policy sane-backends || rpm -q sane-backends || sane-backends --version
2. No fixed release: DOWNGRADE to a release before 1.0.25 (Debian / Ubuntu)
apt-cache madison sane-backends sudo apt install sane-backends=<VERSION_BEFORE_1.0.25> sudo apt-mark hold sane-backends
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list sane-backends sudo dnf downgrade sane-backends-<VERSION_BEFORE_1.0.25> sudo dnf versionlock add sane-backends
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-2017-6318?

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

Is CVE-2017-6318 being exploited?

CVE-2017-6318 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-2017-6318 affect?

CVE-2017-6318 affects leap, sane-backends. Severity is high (CVSS 7.5). saned in sane-backends 1.0.25 allows remote attackers to obtain sensitive memory information via a crafted SANE_NET_CONTROL_OPTION packet.

How urgent is CVE-2017-6318?

Priority 53/100. High severity; Remotely exploitable, no login, no user action

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.