# CVE-2023-50939: IBM PowerSC information Disclosure

> An attacker can decrypt highly sensitive information due to the use of weak cryptographic algorithms in IBM PowerSC.

- **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:** 1 Feb 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-75gj-wpvg-hgcq

## What is CVE-2023-50939?

CVE-2023-50939 is a medium-severity vulnerability in IBM PowerSC, published on 1 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM PowerSC 1.3, 2.0, and 2.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.  IBM X-Force ID:  275129.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 1 product.


Products: Ibm Powersc.

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

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

## Is CVE-2023-50939 being exploited?

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

## Other vulnerabilities in IBM PowerSC

- [CVE-2023-50326](https://insights.sbomify.com/CVE-2023-50326/): IBM PowerSC information Disclosure (high 7.5)
- [CVE-2023-50935](https://insights.sbomify.com/CVE-2023-50935/): IBM PowerSC forced browsing (medium 6.5)
- [CVE-2023-50938](https://insights.sbomify.com/CVE-2023-50938/): IBM PowerSC clickjacking (medium 6.5)
- [CVE-2023-50936](https://insights.sbomify.com/CVE-2023-50936/): IBM PowerSC session fixation (medium 6.3)
- [CVE-2023-50941](https://insights.sbomify.com/CVE-2023-50941/): IBM PowerSC session fixation (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50939 is a medium-severity vulnerability in IBM PowerSC, published on 1 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-50939 in the wild and no public exploit code.

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

## Sources

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

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