# CVE-2008-1926: Other in n/a

> Remote attackers can inject arguments into login logs to hide activities, requiring OS updates to fix the audit log injection flaw.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-1926, DTSA-126-1, GHSA-xj37-vmc7-9w35, RHBA-2009:0070, RHSA-2009:0981

## What is CVE-2008-1926?

CVE-2008-1926 is a high-severity vulnerability in n/a, published on 23 Apr 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Argument injection vulnerability in login (login-utils/login.c) in util-linux-ng 2.14 and earlier makes it easier for remote attackers to hide activities by modifying portions of log events, as demonstrated by appending an "addr=" statement to the login name, aka "audit log injection."

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2008-1926?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `util-linux` | Red Hat:enterprise_linux:4::as | All versions | 0:2.12a-24.el4 |
| `util-linux-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.12a-24.el4 |
| `util-linux` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.12a-24.el4 |
| `util-linux-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.12a-24.el4 |
| `util-linux` | Red Hat:enterprise_linux:4::es | All versions | 0:2.12a-24.el4 |
| `util-linux-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.12a-24.el4 |
| `util-linux` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.12a-24.el4 |
| `util-linux-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.12a-24.el4 |
| `util-linux` | Red Hat:enterprise_linux:5::client | All versions | 0:2.13-0.50.el5 |
| `util-linux-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.13-0.50.el5 |
| `util-linux` | Red Hat:enterprise_linux:5::server | All versions | 0:2.13-0.50.el5 |
| `util-linux-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.13-0.50.el5 |

Products: Linux Util-Linux.

## How do I fix CVE-2008-1926?

Apply the vendor's patch.

## Is CVE-2008-1926 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-1677](https://insights.sbomify.com/CVE-2011-1677/): Denial of service in n/a (medium 4.6)
- [CVE-2011-1675](https://insights.sbomify.com/CVE-2011-1675/): Denial of service in n/a (low 3.3)
- [CVE-2011-1676](https://insights.sbomify.com/CVE-2011-1676/): Denial of service in n/a (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1926 and fix it if it is affected.

What it is: CVE-2008-1926 is a high-severity vulnerability in n/a, published on 23 Apr 2008. 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-2008-1926 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-2008-1926/ (Markdown: https://insights.sbomify.com/CVE-2008-1926/index.md)
```

## Sources

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

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