# CVE-2023-42010: IBM Sterling B2B Integrator Standard Edition information disclosure

> Attackers can disclose sensitive information via man-in-the-middle techniques in IBM Sterling B2B Integrator Standard Edition.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/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 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-2whg-fx75-q3fr

## What is CVE-2023-42010?

CVE-2023-42010 is a low-severity vulnerability in Ibm Sterling B2b Integrator, published on 17 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Sterling B2B Integrator Standard Edition 6.0.0.0 through 6.1.2.5 and 6.2.0.0 through 6.2.0.2 could disclose sensitive information in the HTTP response using man in the middle techniques.  IBM X-Force ID:  265507.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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

It affects 1 product.


Products: Ibm Sterling B2b Integrator.

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

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

## Is CVE-2023-42010 being exploited?

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

## Other vulnerabilities in Ibm Sterling B2b Integrator

- [CVE-2015-7450](https://insights.sbomify.com/CVE-2015-7450/): IBM WebSphere Application Server and Server Hypervisor Edition Code Injection. (critical 9.8, exploited in the wild)
- [CVE-2024-31903](https://insights.sbomify.com/CVE-2024-31903/): IBM Sterling B2B Integrator Standard Edition code execution (high 8.8)
- [CVE-2019-4728](https://insights.sbomify.com/CVE-2019-4728/): Deserialization in Sterling B2B Integrator (high 8.8)
- [CVE-2020-4762](https://insights.sbomify.com/CVE-2020-4762/): Privilege escalation in Sterling B2B Integrator (high 8.8)
- [CVE-2017-1174](https://insights.sbomify.com/CVE-2017-1174/): SQL injection in Sterling B2B Integrator (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-42010 is a low-severity vulnerability in Ibm Sterling B2b Integrator, published on 17 Jul 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-2023-42010 in the wild and no public exploit code.

Affected product: Ibm Sterling B2b Integrator. 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-42010/ (Markdown: https://insights.sbomify.com/CVE-2023-42010/index.md)
```

## Sources

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

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