# CVE-2017-10668: Weak cryptography in n/a

> An attacker in a Man-in-the-Middle position can decrypt transport encryption by exploiting a padding oracle vulnerability in the OSCI Transport Library.

- **Severity:** Medium 5.9 (`CVSS:3.0/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:** 30 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h452-4rxp-px5r

## What is CVE-2017-10668?

CVE-2017-10668 is a medium-severity vulnerability in n/a, published on 30 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Padding Oracle exists in OSCI-Transport 1.2 as used in OSCI Transport Library 1.6.1 (Java) and OSCI Transport Library 1.6 (.NET). Under an MITM condition within the OSCI infrastructure, an attacker needs to send crafted protocol messages to analyse the CBC mode padding in order to decrypt the transport encryption.

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

## Which versions are affected by CVE-2017-10668?

It affects 1 product.


Products: Xoev Osci Transport Library.

## How do I fix CVE-2017-10668?

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

## Is CVE-2017-10668 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-10670](https://insights.sbomify.com/CVE-2017-10670/): XML external entity in n/a (critical 9.8)
- [CVE-2017-10669](https://insights.sbomify.com/CVE-2017-10669/): Other in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10668 and fix it if it is affected.

What it is: CVE-2017-10668 is a medium-severity vulnerability in n/a, published on 30 Jun 2017. 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-2017-10668 in the wild and no public exploit code.

Affected product: n/a. 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-2017-10668/ (Markdown: https://insights.sbomify.com/CVE-2017-10668/index.md)
```

## Sources

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

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