# CVE-2019-4397: Information disclosure in Cloud Orchestrator

> Attackers can access sensitive information stored in URL parameters via logs or history, leading to data disclosure in IBM Cloud Orchestrator.

- **Severity:** Medium 5.3 (`CVSS:3.0/AC:H/UI:N/S:U/PR:L/C:H/A:N/I:N/AV:N/RL:O/RC:C/E:U`)
- **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:** 24 Oct 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-fv6q-cpfx-7rj8

## What is CVE-2019-4397?

CVE-2019-4397 is a medium-severity vulnerability in IBM Cloud Orchestrator, published on 24 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Cloud Orchestrator and IBM Cloud Orchestrator Enterprise 2.5 through 2.5.0.9 and 2.4 through 2.4.0.5 stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referrer header or browser history. IBM X-Force ID: 162239

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 2 products.


Products: Ibm Cloud Orchestrator, Ibm Cloud Orchestrator Enterprise.

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

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

## Is CVE-2019-4397 being exploited?

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

## Other vulnerabilities in IBM Cloud Orchestrator

- [CVE-2016-0204](https://insights.sbomify.com/CVE-2016-0204/): Open redirect in n/a (medium 6.8)
- [CVE-2019-4399](https://insights.sbomify.com/CVE-2019-4399/): Weak cryptography in Cloud Orchestrator (medium 5.9)
- [CVE-2016-0203](https://insights.sbomify.com/CVE-2016-0203/): Information disclosure in Cloud Orchestrator (medium 5.5)
- [CVE-2019-4396](https://insights.sbomify.com/CVE-2019-4396/): Other in Cloud Orchestrator (medium 5.4)
- [CVE-2019-4461](https://insights.sbomify.com/CVE-2019-4461/): Other in Cloud Orchestrator (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-4397 is a medium-severity vulnerability in IBM Cloud Orchestrator, published on 24 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-4397 in the wild and no public exploit code.

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

## Sources

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

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