CVE-2003-0776: High severity SANE SANE vulnerability
Published Sep 12, 2003
·Updated
saned in sane-backends 1.0.7 and earlier does not properly "check the validity of the RPC numbers it gets before getting the parameters," with unknown consequences.
Affected Software
13 affected components
SANE SANE=1.0.0
SANE SANE=1.0.1
SANE SANE=1.0.2
SANE SANE=1.0.3
SANE SANE=1.0.4
SANE SANE=1.0.5
SANE SANE=1.0.6
SANE SANE=1.0.7
SANE SANE=1.0.7_beta1
SANE SANE=1.0.7_beta2
SANE SANE=1.0.8
SANE SANE=1.0.9
SANE sane-backend=1.0.10
Remediation
Patch Available
Patch Available
Event History
Sep 12, 2003
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Sep 22, 2003
Data Sourced
via NVD·04:00 AM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2003-0776?
CVE-2003-0776 has an unknown severity due to the lack of detailed consequences from the vulnerability.
2
How do I fix CVE-2003-0776?
To mitigate CVE-2003-0776, upgrade to a version of sane-backends later than 1.0.8.
3
Which versions are affected by CVE-2003-0776?
CVE-2003-0776 affects sane-backends versions 1.0.0 through 1.0.8.
4
What type of vulnerability is CVE-2003-0776?
CVE-2003-0776 is a vulnerability in the RPC handling of the saned service in sane-backends.
5
Is CVE-2003-0776 exploitable remotely?
The exploitability of CVE-2003-0776 is unclear due to its vague description regarding consequences.