# CVE-2003-0776: Other in n/a

> The saned daemon fails to validate RPC numbers, potentially leading to undefined behavior or crashes when processing network requests.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Sep 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0776, GHSA-pf42-5v8g-g3xx

## What is CVE-2003-0776?

CVE-2003-0776 is a high-severity vulnerability in n/a, published on 12 Sep 2003. It can be exploited over the network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2003-0776?

It affects 2 products.


Products: Sane Sane, Sane Sane-Backend.

## How do I fix CVE-2003-0776?

Upgrade to a fixed version.

## Is CVE-2003-0776 being exploited?

There is no known exploitation of CVE-2003-0776 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2003-0773](https://insights.sbomify.com/CVE-2003-0773/): Missing authorization in n/a (high 7.5)
- [CVE-2003-0774](https://insights.sbomify.com/CVE-2003-0774/): Denial of service in n/a (high 7.5)
- [CVE-2003-0775](https://insights.sbomify.com/CVE-2003-0775/): Denial of service in n/a (medium 5.0)
- [CVE-2003-0777](https://insights.sbomify.com/CVE-2003-0777/): Denial of service in n/a (medium 5.0)
- [CVE-2003-0778](https://insights.sbomify.com/CVE-2003-0778/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0776 and fix it if it is affected.

What it is: CVE-2003-0776 is a high-severity vulnerability in n/a, published on 12 Sep 2003. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0776 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2003-0776/ (Markdown: https://insights.sbomify.com/CVE-2003-0776/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2003-0776
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2003-0776
- OSV: https://osv.dev/vulnerability/CVE-2003-0776

---
From sbomify Insights: https://insights.sbomify.com/CVE-2003-0776/
Summaries are generated and may contain mistakes; the official description above is the record.