ubuntu-cve-2023-6935
Vulnerability from osv_ubuntu
wolfSSL SP Math All RSA implementation is vulnerable to the Marvin Attack, new variation of a timing Bleichenbacher style attack, when built with the following options to configure: --enable-all CFLAGS="-DWOLFSSL_STATIC_RSA" The define “WOLFSSL_STATIC_RSA” enables static RSA cipher suites, which is not recommended, and has been disabled by default since wolfSSL 3.6.6. Therefore the default build since 3.6.6, even with "--enable-all", is not vulnerable to the Marvin Attack. The vulnerability is specific to static RSA cipher suites, and expected to be padding-independent. The vulnerability allows an attacker to decrypt ciphertexts and forge signatures after probing with a large number of test observations. However the server’s private key is not exposed.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libcyassl5",
"binary_version": "3.4.8+dfsg-1"
},
{
"binary_name": "libwolfssl0",
"binary_version": "3.4.8+dfsg-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "wolfssl",
"purl": "pkg:deb/ubuntu/wolfssl@3.4.8+dfsg-1?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.4.8+dfsg-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwolfssl15",
"binary_version": "3.13.0+dfsg-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "wolfssl",
"purl": "pkg:deb/ubuntu/wolfssl@3.13.0+dfsg-1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.10.2+dfsg-2",
"3.12.0+dfsg-1",
"3.12.2+dfsg-1",
"3.13.0+dfsg-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwolfssl24",
"binary_version": "4.3.0+dfsg-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "wolfssl",
"purl": "pkg:deb/ubuntu/wolfssl@4.3.0+dfsg-2?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.1.0+dfsg-2",
"4.2.0+dfsg-1",
"4.2.0+dfsg-2",
"4.2.0+dfsg-3",
"4.3.0+dfsg-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwolfssl32",
"binary_version": "5.2.0-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "wolfssl",
"purl": "pkg:deb/ubuntu/wolfssl@5.2.0-2?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.6.0-3",
"5.0.0-1",
"5.1.1-1",
"5.2.0-1",
"5.2.0-2"
]
}
],
"aliases": [],
"details": "wolfSSL SP Math All RSA implementation is vulnerable to the Marvin Attack, new variation of a timing Bleichenbacher style attack, when built with the following options to configure: --enable-all CFLAGS=\"-DWOLFSSL_STATIC_RSA\" The define \u201cWOLFSSL_STATIC_RSA\u201d enables static RSA cipher suites, which is not recommended, and has been disabled by default since wolfSSL 3.6.6. Therefore the default build since 3.6.6, even with \"--enable-all\", is not vulnerable to the Marvin Attack. The vulnerability is specific to static RSA cipher suites, and expected to be padding-independent. The vulnerability allows an attacker to decrypt ciphertexts and forge signatures after probing with a large number of test observations. However the server\u2019s private key is not exposed.",
"id": "UBUNTU-CVE-2023-6935",
"modified": "2026-04-22T07:45:11Z",
"published": "2024-02-09T23:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2023-6935"
},
{
"type": "REPORT",
"url": "https://github.com/wolfSSL/wolfssl/blob/v5.6.6-stable/ChangeLog.md#vulnerabilities"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-6935"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2023-6935"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.