# CVE-2014-3012: Other in n/a

> Authenticated attackers can inject HTTP headers and split responses in IBM Curam Social Program Management via custom JSPs.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/I:P/A:N`)
- **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:** 18 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5fpr-j2j4-f36c

## What is CVE-2014-3012?

CVE-2014-3012 is a low-severity vulnerability in n/a, published on 18 Jun 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple CRLF injection vulnerabilities in IBM Curam Social Program Management 5.2 SP1 through 6.0.5.4 allow remote authenticated users to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via unspecified parameters to custom JSPs.

## Which versions are affected by CVE-2014-3012?

It affects 1 product.


Products: Ibm Curam Social Program Management.

## How do I fix CVE-2014-3012?

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

## Is CVE-2014-3012 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-6111](https://insights.sbomify.com/CVE-2016-6111/): XML external entity in Cram Social Program Management (critical 9.1)
- [CVE-2014-8903](https://insights.sbomify.com/CVE-2014-8903/): Code injection in n/a (high 8.8)
- [CVE-2020-4779](https://insights.sbomify.com/CVE-2020-4779/): Auth bypass in Curam SPM (high 8.1)
- [CVE-2020-4772](https://insights.sbomify.com/CVE-2020-4772/): XML external entity in Curam SPM (high 7.1)
- [CVE-2018-1654](https://insights.sbomify.com/CVE-2018-1654/): Open redirect in Curam Social Program Management (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3012 and fix it if it is affected.

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

## Sources

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

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