# CVE-2006-7108: Auth bypass in n/a

> Attackers can bypass account management policies during Kerberos login sessions, allowing unauthorized access despite intended restrictions.

- **Severity:** Medium 4.1 (`AV:L/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-7108, GHSA-224c-qxxc-fqx7, RHSA-2007:0235

## What is CVE-2006-7108?

CVE-2006-7108 is a medium-severity authentication bypass vulnerability in n/a, published on 4 Mar 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

login in util-linux-2.12a skips pam_acct_mgmt and chauth_tok when authentication is skipped, such as when a Kerberos krlogin session has been established, which might allow users to bypass intended access policies that would be enforced by pam_acct_mgmt and chauth_tok.

Weakness: CWE-264

## Which versions are affected by CVE-2006-7108?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `util-linux` | Red Hat:enterprise_linux:4::as | All versions | 0:2.12a-16.EL4.25 |
| `util-linux-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.12a-16.EL4.25 |
| `util-linux` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.12a-16.EL4.25 |
| `util-linux-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.12a-16.EL4.25 |
| `util-linux` | Red Hat:enterprise_linux:4::es | All versions | 0:2.12a-16.EL4.25 |
| `util-linux-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.12a-16.EL4.25 |
| `util-linux` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.12a-16.EL4.25 |
| `util-linux-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.12a-16.EL4.25 |

Products: Andries Brouwer Util-Linux.

## How do I fix CVE-2006-7108?

Apply the vendor's patch.

## Is CVE-2006-7108 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2876](https://insights.sbomify.com/CVE-2005-2876/): Privilege escalation in n/a (high 7.2)
- [CVE-2001-1147](https://insights.sbomify.com/CVE-2001-1147/): Information disclosure in n/a (high 7.2)
- [CVE-2001-1175](https://insights.sbomify.com/CVE-2001-1175/): Information disclosure in n/a (high 7.2)
- [CVE-2003-0094](https://insights.sbomify.com/CVE-2003-0094/): Weak cryptography in n/a (medium 5.0)
- [CVE-2004-0080](https://insights.sbomify.com/CVE-2004-0080/): Use after free in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7108 and fix it if it is affected.

What it is: CVE-2006-7108 is a medium-severity authentication bypass vulnerability in n/a, published on 4 Mar 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-7108 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-2006-7108/ (Markdown: https://insights.sbomify.com/CVE-2006-7108/index.md)
```

## Sources

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

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