CVE-2013-1623 The TLS and DTLS implementations in wolfSSL CyaSSL before 2.5.0 do not properly consider timing side-channel attacks on a noncompliant MAC c
Medium 4.3
Published
Updated
Check this codebase for CVE-2013-1623 and fix it if it is affected.
What it is: CVE-2013-1623 is a medium-severity vulnerability in n/a, published on 8 Feb 2013.
Exploitation: There is no known exploitation of CVE-2013-1623 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-2013-1623/ (Markdown: https://insights.sbomify.com/CVE-2013-1623/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2013-1623?
CVE-2013-1623 is a medium-severity vulnerability in n/a, published on 8 Feb 2013.
Official description
The TLS and DTLS implementations in wolfSSL CyaSSL before 2.5.0 do not properly consider timing side-channel attacks on a noncompliant MAC check operation during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data for crafted packets, a related issue to CVE-2013-0169.
Weakness: CWE-310
Which versions are affected by CVE-2013-1623?
It affects 1 product.
Products include Yassl Cyassl.
How do I fix CVE-2013-1623?
Upgrade to a fixed version.
Is CVE-2013-1623 being exploited?
There is no known exploitation of CVE-2013-1623 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-5g8p-qpcj-85w5.