# CVE-2005-4579: Other in n/a

> Remote attackers can inject arbitrary HTTP headers via response splitting in Hitachi BLC, potentially modifying responses or bypassing security controls.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7j29-8px4-p3vh

## What is CVE-2005-4579?

CVE-2005-4579 is a medium-severity vulnerability in n/a, published on 29 Dec 2005. It can be exploited over the network, with no action from the victim.

### Official description

Multiple HTTP response splitting vulnerabilities in Hitachi Business Logic - Container (BLC) P-2443-9114 01-00 through 02-06 on Windows, and P-1M43-9111 01-01 through 02-00 on AIX, allow remote attackers to inject arbitrary HTTP headers via unknown attack vectors in an unspecified input form.

## Which versions are affected by CVE-2005-4579?

It affects 1 product.


Products: Hitachi Business Logic.

## How do I fix CVE-2005-4579?

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

## Is CVE-2005-4579 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0772](https://insights.sbomify.com/CVE-2006-0772/): SQL injection in n/a (high 7.5)
- [CVE-2005-4578](https://insights.sbomify.com/CVE-2005-4578/): SQL injection in n/a (high 7.5)
- [CVE-2006-0773](https://insights.sbomify.com/CVE-2006-0773/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2005-4577](https://insights.sbomify.com/CVE-2005-4577/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4579 and fix it if it is affected.

What it is: CVE-2005-4579 is a medium-severity vulnerability in n/a, published on 29 Dec 2005. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4579 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-2005-4579/ (Markdown: https://insights.sbomify.com/CVE-2005-4579/index.md)
```

## Sources

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

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