CVE-2009-0242 gmetad in Ganglia 3.1.1, when supporting multiple requests per connection on an interactive port, allows remote attackers to cause a denial
Not scored
Published
Updated
Check this codebase for CVE-2009-0242 and fix it if it is affected.
What it is: CVE-2009-0242 is a vulnerability, published on 21 Jan 2009.
Exploitation: There is no known exploitation of CVE-2009-0242 in the wild and no public exploit code.
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-0242/ (Markdown: https://insights.sbomify.com/CVE-2009-0242/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2009-0242?
CVE-2009-0242 is a vulnerability, published on 21 Jan 2009.
Official description
gmetad in Ganglia 3.1.1, when supporting multiple requests per connection on an interactive port, allows remote attackers to cause a denial of service via a request to the gmetad service with a path that does not exist, which causes Ganglia to (1) perform excessive CPU computation and (2) send the entire tree, which consumes network bandwidth. NOTE: the vendor and original researcher have disputed this issue, since legitimate requests can generate the same amount of resource consumption. CVE concurs with the dispute, so this identifier should not be used
Which versions are affected by CVE-2009-0242?
How do I fix CVE-2009-0242?
No fix has been published for CVE-2009-0242 yet. Limit exposure of the affected software until one is available.
Is CVE-2009-0242 being exploited?
There is no known exploitation of CVE-2009-0242 in the wild and no public exploit code.