# CVE-2003-0935: Missing authorization in n/a

> Net-SNMP allows unauthorized users to read restricted MIB data due to missing authorization checks, exposing sensitive network configuration information.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Nov 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0935, GHSA-xm65-9x7h-29gw, RHSA-2004:023

## What is CVE-2003-0935?

CVE-2003-0935 is a medium-severity missing authorization vulnerability in n/a, published on 12 Nov 2003. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Net-SNMP before 5.0.9 allows a user or community to access data in MIB objects, even if that data is not allowed to be viewed.

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `net-snmp` | Red Hat:enterprise_linux:3::as | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-perl` | Red Hat:enterprise_linux:3::as | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-utils` | Red Hat:enterprise_linux:3::as | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp` | Red Hat:enterprise_linux:3::desktop | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-perl` | Red Hat:enterprise_linux:3::desktop | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-utils` | Red Hat:enterprise_linux:3::desktop | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp` | Red Hat:enterprise_linux:3::es | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-perl` | Red Hat:enterprise_linux:3::es | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-utils` | Red Hat:enterprise_linux:3::es | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp` | Red Hat:enterprise_linux:3::ws | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-perl` | Red Hat:enterprise_linux:3::ws | All versions | 0:5.0.9-2.30E.1 |
| `net-snmp-utils` | Red Hat:enterprise_linux:3::ws | All versions | 0:5.0.9-2.30E.1 |

Products: Net-Snmp Net-Snmp.

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

Upgrade to a fixed version.

## Is CVE-2003-0935 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4837](https://insights.sbomify.com/CVE-2005-4837/): Use after free in n/a (critical 10.0)
- [CVE-2005-1740](https://insights.sbomify.com/CVE-2005-1740/): Path traversal in n/a (critical 10.0)
- [CVE-2007-5846](https://insights.sbomify.com/CVE-2007-5846/): Denial of service in n/a (high 7.8)
- [CVE-2018-18066](https://insights.sbomify.com/CVE-2018-18066/): Null dereference in n/a (high 7.5)
- [CVE-2015-5621](https://insights.sbomify.com/CVE-2015-5621/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0935 is a medium-severity missing authorization vulnerability in n/a, published on 12 Nov 2003. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0935 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-0935/ (Markdown: https://insights.sbomify.com/CVE-2003-0935/index.md)
```

## Sources

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

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