# CVE-2003-0461: /proc/tty/driver/serial in Linux 2.4.x reveals the exact number of characters used in serial links, which could allow local users to obtain


- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 25 Jul 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-8x73-xrpj-qfx7

## What is CVE-2003-0461?

CVE-2003-0461 is a low-severity vulnerability in Redhat Linux, published on 25 Jul 2003. 

### Official description

/proc/tty/driver/serial in Linux 2.4.x reveals the exact number of characters used in serial links, which could allow local users to obtain potentially sensitive information such as the length of passwords.

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

It affects 1 product.


Products: Redhat Linux.

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

Upgrade to a fixed version.

## Is CVE-2003-0461 being exploited?

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

## Other vulnerabilities in Redhat Linux

- [CVE-2000-1220](https://insights.sbomify.com/CVE-2000-1220/): Privilege escalation in n/a (critical 10.0)
- [CVE-2003-0248](https://insights.sbomify.com/CVE-2003-0248/): Privilege escalation in n/a (critical 10.0)
- [CVE-1999-1542](https://insights.sbomify.com/CVE-1999-1542/): Command injection in n/a (critical 10.0)
- [CVE-1999-1299](https://insights.sbomify.com/CVE-1999-1299/): Privilege escalation in n/a (critical 10.0)
- [CVE-2000-0322](https://insights.sbomify.com/CVE-2000-0322/): Command injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0461 is a low-severity vulnerability in Redhat Linux, published on 25 Jul 2003. 
Exploitation: There is no known exploitation of CVE-2003-0461 in the wild and no public exploit code.

Affected product: Redhat Linux. 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-0461/ (Markdown: https://insights.sbomify.com/CVE-2003-0461/index.md)
```

## Sources

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

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