# CVE-2019-4552: Other in Security Access Manager

> Remote attackers can exploit HTTP response splitting via crafted URLs to poison caches, inject scripts, or steal sensitive information.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/C:L/PR:N/A:N/S:C/I:L/UI:R/AC:L/RL:O/RC:C/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Oct 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5g4v-ppfj-47wj

## What is CVE-2019-4552?

CVE-2019-4552 is a medium-severity vulnerability in Ibm Security Verify Access, published on 15 Oct 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

IBM Security Access Manager 9.0.7 and IBM Security Verify Access 10.0.0 are vulnerable to HTTP response splitting attacks. A remote attacker could exploit this vulnerability using specially-crafted URL to cause the server to return a split response, once the URL is clicked. This would allow the attacker to perform further attacks, such as Web cache poisoning, cross-site scripting, and possibly obtain sensitive information. IBM X-Force ID: 165960.

## Which versions are affected by CVE-2019-4552?

It affects 2 products.


Products: Ibm Security Access Manager, Ibm Security Verify Access.

## How do I fix CVE-2019-4552?

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

## Is CVE-2019-4552 being exploited?

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

## Other vulnerabilities in Ibm Security Verify Access

- [CVE-2018-1722](https://insights.sbomify.com/CVE-2018-1722/): Code injection in Security Access Manager Appliance (critical 10.0)
- [CVE-2016-3028](https://insights.sbomify.com/CVE-2016-3028/): Command injection in n/a (critical 9.1)
- [CVE-2018-1850](https://insights.sbomify.com/CVE-2018-1850/): Missing authorization in Security Access Manager Appliance (high 8.8)
- [CVE-2016-3025](https://insights.sbomify.com/CVE-2016-3025/): Security feature bypass in n/a (high 8.1)
- [CVE-2023-30997](https://insights.sbomify.com/CVE-2023-30997/): IBM Security Access Manager Docker privilege escalation (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-4552 and fix it if it is affected.

What it is: CVE-2019-4552 is a medium-severity vulnerability in Ibm Security Verify Access, published on 15 Oct 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-4552 in the wild and no public exploit code.

Affected product: Ibm Security Verify Access. 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-2019-4552/ (Markdown: https://insights.sbomify.com/CVE-2019-4552/index.md)
```

## Sources

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

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