CVE-2003-0776
UnknownEPSS 1.76%
Last modified
CVE-2003-0776 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.76% chance of exploitation in the next 30 days.
Description
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.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| 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 |
References
- http://www.debian.org/security/2003/dsa-379Exploit, Patch, Vendor Advisory
- http://www.redhat.com/support/errata/RHSA-2003-278.htmlPatch, Vendor Advisory
- http://www.debian.org/security/2003/dsa-379Exploit, Patch, Vendor Advisory
- http://www.redhat.com/support/errata/RHSA-2003-278.htmlPatch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2003-0776?
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.
How severe is CVE-2003-0776?
Severity scoring for CVE-2003-0776 is pending analysis. The EPSS model estimates a 1.76% probability of exploitation in the next 30 days.
How do I fix CVE-2003-0776?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2003-0776?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST