# CVE-2018-1943: Other in Cloud Private

> Attackers can inject HTTP headers via crafted pages, enabling XSS, cache poisoning, or session hijacking in IBM Cloud Private.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/UI:R/S:C/C:L/AC:L/I:L/PR:L/A:N/RC:C/E:U/RL:O`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Apr 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-74v2-5mpp-xhc7

## What is CVE-2018-1943?

CVE-2018-1943 is a medium-severity vulnerability in IBM Cloud Private, published on 8 Apr 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

IBM Cloud Private 3.1.0 and 3.1.1 is vulnerable to HTTP HOST header injection, caused by improper validation of input. By persuading a victim to visit a specially-crafted Web page, a remote attacker could exploit this vulnerability to inject arbitrary HTTP headers, which will allow the attacker to conduct various attacks against the vulnerable system, including cross-site scripting, cache poisoning or session hijacking. IBM X-Force ID: 153385.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2018-1943?

It affects 1 product.


Products: Ibm Cloud Private.

## How do I fix CVE-2018-1943?

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

## Is CVE-2018-1943 being exploited?

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

## Other vulnerabilities in IBM Cloud Private

- [CVE-2018-1939](https://insights.sbomify.com/CVE-2018-1939/): Open redirect in Cloud Private (medium 6.8)
- [CVE-2019-4239](https://insights.sbomify.com/CVE-2019-4239/): Information disclosure in MQ Advanced Cloud Pak (IBM Cloud Private on RedHat OpenShift) (medium 6.2)
- [CVE-2018-1841](https://insights.sbomify.com/CVE-2018-1841/): Information disclosure in Cloud Private (medium 6.2)
- [CVE-2019-4439](https://insights.sbomify.com/CVE-2019-4439/): Auth bypass in Cloud Private (medium 5.9)
- [CVE-2019-4116](https://insights.sbomify.com/CVE-2019-4116/): Information disclosure in Cloud Private (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1943 and fix it if it is affected.

What it is: CVE-2018-1943 is a medium-severity vulnerability in IBM Cloud Private, published on 8 Apr 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1943 in the wild and no public exploit code.

Affected product: IBM Cloud Private. 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-2018-1943/ (Markdown: https://insights.sbomify.com/CVE-2018-1943/index.md)
```

## Sources

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

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