# CVE-2009-1197: Other in n/a

> Attackers can spoof log entries in Apache jUDDI via error logging vectors, potentially misleading security audits or hiding malicious activity.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 30 Oct 2017
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9prw-859c-gqxh

## What is CVE-2009-1197?

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

### Official description

Apache jUDDI before 2.0 allows attackers to spoof entries in log files via vectors related to error logging of keys from uddiget.jsp.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Apache Juddi.

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

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

## Is CVE-2009-1197 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-37578](https://insights.sbomify.com/CVE-2021-37578/): Remote code execution via RMI (critical 9.8)
- [CVE-2018-1307](https://insights.sbomify.com/CVE-2018-1307/): Apache juddi-client vulnerable to XML External Entity (XXE) (high 8.1)
- [CVE-2009-4267](https://insights.sbomify.com/CVE-2009-4267/): Other in jUDDI (medium 6.5)
- [CVE-2009-1198](https://insights.sbomify.com/CVE-2009-1198/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2015-5241](https://insights.sbomify.com/CVE-2015-5241/): Moderate severity vulnerability that affects org.apache.juddi:juddi-client (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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