# CVE-2008-5617: Auth bypass in n/a

> Remote attackers can bypass ACL restrictions in rsyslog to spoof log messages or cause denial of service by flooding logs.

- **Severity:** High 8.5 (`AV:N/AC:L/Au:N/C:N/I:P/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Dec 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-5617, GHSA-8fh8-56w4-443q

## What is CVE-2008-5617?

CVE-2008-5617 is a high-severity authentication bypass vulnerability in n/a, published on 17 Dec 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ACL handling in rsyslog 3.12.1 to 3.20.0, 4.1.0, and 4.1.1 does not follow $AllowedSender directive, which allows remote attackers to bypass intended access restrictions and spoof log messages or create a large number of spurious messages.

Weakness: CWE-264

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

It affects 1 product.


Products: Rsyslog Rsyslog.

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

Upgrade to a fixed version.

## Is CVE-2008-5617 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-17040](https://insights.sbomify.com/CVE-2019-17040/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-12588](https://insights.sbomify.com/CVE-2017-12588/): Other in n/a (critical 9.8)
- [CVE-2014-3634](https://insights.sbomify.com/CVE-2014-3634/): Memory corruption in n/a (high 7.5)
- [CVE-2013-4758](https://insights.sbomify.com/CVE-2013-4758/): Use after free in n/a (medium 6.8)
- [CVE-2015-3243](https://insights.sbomify.com/CVE-2015-3243/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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