# CVE-2023-38372: IBM Watson IoT Platform information disclosure

> An attacker with a stolen authentication token can impersonate authorized users on the IBM Watson IoT Platform, leading to unauthorized access and data exposure.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Feb 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-73mf-287p-8r8c

## What is CVE-2023-38372?

CVE-2023-38372 is a medium-severity authentication bypass vulnerability in IBM Watson IoT Platform, published on 29 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthorized attacker who has obtained an IBM Watson IoT Platform 1.0 security authentication token can use it to impersonate an authorized platform user.  IBM X-Force ID:  261201.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-38372?

It affects 1 product.


Products: Ibm Watson Iot Platform.

## How do I fix CVE-2023-38372?

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

## Is CVE-2023-38372 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-38372 and fix it if it is affected.

What it is: CVE-2023-38372 is a medium-severity authentication bypass vulnerability in IBM Watson IoT Platform, published on 29 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-38372 in the wild and no public exploit code.

Affected product: IBM Watson IoT Platform. 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-2023-38372/ (Markdown: https://insights.sbomify.com/CVE-2023-38372/index.md)
```

## Sources

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

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