# CVE-2009-3568: Missing authorization in n/a

> Remote attackers can read sensitive node titles and content via RSS feeds due to missing permission checks in the Comment RSS module.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-62wr-q7q7-4f5m

## What is CVE-2009-3568?

CVE-2009-3568 is a medium-severity missing authorization vulnerability in n/a, published on 6 Oct 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Comment RSS 5.x before 5.x-2.2 and 6.x before 6.x-2.2, a module for Drupal, does not properly enforce permissions when a link is added to the RSS feed, which allows remote attackers to obtain the node title and possibly other sensitive content by reading the feed.

Weakness: CWE-264

## Which versions are affected by CVE-2009-3568?

It affects 2 products.


Products: Dave Reid Commentrss, Gabor Hojtsy Commentrss.

## How do I fix CVE-2009-3568?

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

## Is CVE-2009-3568 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3568 and fix it if it is affected.

What it is: CVE-2009-3568 is a medium-severity missing authorization vulnerability in n/a, published on 6 Oct 2009. 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-2009-3568 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-2009-3568/ (Markdown: https://insights.sbomify.com/CVE-2009-3568/index.md)
```

## Sources

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

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