# CVE-2008-3033: Missing authorization in n/a

> Remote attackers can access administrative functions without authentication, leading to privilege escalation and data modification.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6x3f-5896-c4jp

## What is CVE-2008-3033?

CVE-2008-3033 is a critical missing authorization vulnerability in n/a, published on 7 Jul 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RSS-aggregator 1.0 does not require administrative authentication for the admin/fonctions/ directory, which allows remote attackers to access admin functions and have unspecified other impact, as demonstrated by (1) an IdFlux request to supprimer_flux.php and (2) a TpsRafraich request to modifier_tps_rafraich.php.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Rss Aggregator Rss Aggregator.

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

No fix has been published for CVE-2008-3033 yet. Limit exposure of the affected software until one is available.

## Is CVE-2008-3033 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-3033 exists.

Public exploit code:

- RSS-aggregator 1.0 - Authentication Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-2884](https://insights.sbomify.com/CVE-2008-2884/): Code injection in n/a (critical 9.3)
- [CVE-2008-3034](https://insights.sbomify.com/CVE-2008-3034/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-3033 is a critical missing authorization vulnerability in n/a, published on 7 Jul 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-3033 exists.

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-3033/ (Markdown: https://insights.sbomify.com/CVE-2008-3033/index.md)
```

## Sources

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

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