CVE-2017-10668
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA Padding Oracle vulnerability exists in OSCI-Transport 1.2 as implemented in OSCI Transport Library 1.6.1 (Java) and 1.6 (.NET). An attacker positioned as MITM can craft protocol messages to analyze CBC mode padding responses, enabling decryption of transport encryption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.6= 1.6.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Xoev Osci Transport Library usageSearch your application dependencies, build files (Maven pom.xml, NuGet packages.config, or similar), or installed libraries for 'Xoev Osci Transport Library' or 'OSCI Transport Library'. This library is used for government/e-government transport protocols.Affected if The library is present in your environment
-
Determine the installed versionCheck the version number of the Xoev Osci Transport Library in your dependency manifest or installed packages. Look for version 1.6 (.NET) or 1.6.1 (Java).Affected if The installed version is 1.6 or 1.6.1
-
Verify CBC mode encryption is in useLocate the encryption configuration for your OSCI Transport implementation. Look for cipher configuration settings that specify CBC mode (such as AES/CBC/PKCS5Padding or similar). Check transport configuration files for the encryption algorithm and mode setting.Affected if CBC mode encryption is configured for the OSCI Transport communication
-
Confirm padding oracle exposureTest whether your OSCI Transport endpoint returns distinguishable error messages or responses when receiving invalid padding versus valid padding. An oracle exists if the system reveals whether padding is correct or incorrect through timing differences or distinct error messages.Affected if The system exposes padding validation information through observable differences in responses
You are affected if your environment uses Xoev Osci Transport Library version 1.6 or 1.6.1 with CBC mode encryption enabled, where padding validation responses are observable to an attacker.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace CBC mode with authenticated encryption (e.g., AES-GCM) or implement proper padding validation that prevents oracle behavior to eliminate the attack vector.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10668 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-10668 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data