# CVE-2012-0862: Auth bypass in n/a

> Remote attackers can bypass access restrictions and expose enabled services by sending requests to the tcpmux port when the tcpmux-server service is enabled.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-0862, GHSA-mv4c-6fpc-r32q, RHSA-2013:0499, RHSA-2013:1302

## What is CVE-2012-0862?

CVE-2012-0862 is a medium-severity authentication bypass vulnerability in n/a, published on 4 Jun 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

builtins.c in Xinetd before 2.3.15 does not check the service type when the tcpmux-server service is enabled, which exposes all enabled services and allows remote attackers to bypass intended access restrictions via a request to tcpmux port 1.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2012-0862?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xinetd` | Red Hat:enterprise_linux:5::client | All versions | 2:2.3.14-19.el5 |
| `xinetd-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 2:2.3.14-19.el5 |
| `xinetd` | Red Hat:enterprise_linux:5::server | All versions | 2:2.3.14-19.el5 |
| `xinetd-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 2:2.3.14-19.el5 |
| `xinetd` | Red Hat:enterprise_linux:6::client | All versions | 2:2.3.14-38.el6 |
| `xinetd-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 2:2.3.14-38.el6 |
| `xinetd` | Red Hat:enterprise_linux:6::computenode | All versions | 2:2.3.14-38.el6 |
| `xinetd-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 2:2.3.14-38.el6 |
| `xinetd` | Red Hat:enterprise_linux:6::server | All versions | 2:2.3.14-38.el6 |
| `xinetd-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 2:2.3.14-38.el6 |
| `xinetd` | Red Hat:enterprise_linux:6::workstation | All versions | 2:2.3.14-38.el6 |
| `xinetd-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 2:2.3.14-38.el6 |

Products: Xinetd Xinetd.

## How do I fix CVE-2012-0862?

Upgrade to a fixed version.

## Is CVE-2012-0862 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-0825](https://insights.sbomify.com/CVE-2001-0825/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-1389](https://insights.sbomify.com/CVE-2001-1389/): Memory corruption in n/a (high 7.5)
- [CVE-2000-0536](https://insights.sbomify.com/CVE-2000-0536/): Auth bypass in n/a (high 7.5)
- [CVE-2003-0211](https://insights.sbomify.com/CVE-2003-0211/): Denial of service in n/a (medium 5.0)
- [CVE-2001-1322](https://insights.sbomify.com/CVE-2001-1322/): Misconfiguration in n/a (low 3.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0862 and fix it if it is affected.

What it is: CVE-2012-0862 is a medium-severity authentication bypass vulnerability in n/a, published on 4 Jun 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-0862 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-2012-0862/ (Markdown: https://insights.sbomify.com/CVE-2012-0862/index.md)
```

## Sources

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

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