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

> Remote attackers can bypass access restrictions in the Drupal Aggregation module when node access modules are enabled, potentially reading unauthorized content.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x5x8-54j8-pvh6

## What is CVE-2008-3000?

CVE-2008-3000 is a medium-severity missing authorization vulnerability in n/a, published on 3 Jul 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Aggregation module 5.x before 5.x-4.4 for Drupal, when node access modules are used, does not properly implement access control, which allows remote attackers to bypass intended restrictions.

Weakness: CWE-264

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

It affects 1 product.


Products: Drupal Aggregation Module.

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

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

## Is CVE-2008-3000 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-3001](https://insights.sbomify.com/CVE-2008-3001/): File upload in n/a (critical 9.3)
- [CVE-2008-2999](https://insights.sbomify.com/CVE-2008-2999/): SQL injection in n/a (high 7.5)
- [CVE-2008-2998](https://insights.sbomify.com/CVE-2008-2998/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-3000 is a medium-severity missing authorization vulnerability in n/a, published on 3 Jul 2008. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-3000 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-3000/ (Markdown: https://insights.sbomify.com/CVE-2008-3000/index.md)
```

## Sources

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

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