# CVE-2024-49818: IBM Security Guardium Key Lifecycle Manager information disclosure

> Remote attackers can obtain sensitive information via detailed error messages in IBM Security Guardium Key Lifecycle Manager, aiding further attacks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 17 Dec 2024
- **Updated:** 17 Dec 2024
- **Also known as:** GHSA-xhw8-46vj-3gq5

## What is CVE-2024-49818?

CVE-2024-49818 is a medium-severity vulnerability in IBM Security Guardium Key Lifecycle Manager, published on 17 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 

could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2024-49818?

It affects 1 product.


Products: Ibm Security Guardium Key Lifecycle Manager.

## How do I fix CVE-2024-49818?

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

## Is CVE-2024-49818 being exploited?

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

## Other vulnerabilities in IBM Security Guardium Key Lifecycle Manager

- [CVE-2023-25921](https://insights.sbomify.com/CVE-2023-25921/): IBM Security Guardium Key Lifecycle Manager file upload (high 8.5)
- [CVE-2023-25925](https://insights.sbomify.com/CVE-2023-25925/): IBM Security Guardium Key Lifecycle Manager command injection (high 8.5)
- [CVE-2023-47706](https://insights.sbomify.com/CVE-2023-47706/): IBM Security Guardium Key Lifecycle Manager file upload (medium 6.6)
- [CVE-2021-38976](https://insights.sbomify.com/CVE-2021-38976/): Hardcoded credentials in Security Key Lifecycle Manager (medium 6.2)
- [CVE-2021-38978](https://insights.sbomify.com/CVE-2021-38978/): Information disclosure in Security Key Lifecycle Manager (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-49818 and fix it if it is affected.

What it is: CVE-2024-49818 is a medium-severity vulnerability in IBM Security Guardium Key Lifecycle Manager, published on 17 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-49818 in the wild and no public exploit code.

Affected product: IBM Security Guardium Key Lifecycle Manager. 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-2024-49818/ (Markdown: https://insights.sbomify.com/CVE-2024-49818/index.md)
```

## Sources

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

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