# CVE-2019-1559: 0-byte record padding oracle > A padding oracle in OpenSSL allows remote attackers to decrypt data if specific non-stitched ciphersuites are used and the application mishandles SSL shutdown errors. - **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:** Yes - **Published:** 27 Feb 2019 - **Updated:** 17 Sep 2024 - **Also known as:** ALPINE-CVE-2019-1559, DEBIAN-CVE-2019-1559, DLA-1701-1, DSA-4400-1, GHSA-9ccq-7hvh-cv7p, MGASA-2019-0106, RHSA-2019:2471, SUSE-SU-2019:0572-1, SUSE-SU-2019:0600-1, SUSE-SU-2019:0803-1, SUSE-SU-2019:1362-1, SUSE-SU-2019:14091-1, SUSE-SU-2019:14092-1, SUSE-SU-2019:1608-1, UBUNTU-CVE-2019-1559, USN-3899-1, openSUSE-SU-2019:1105-1, openSUSE-SU-2019:1432-1 ## What is CVE-2019-1559? CVE-2019-1559 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 27 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding compared to if a 0 byte record is received with an invalid MAC. If the application then behaves differently based on that in a way that is detectable to the remote peer, then this amounts to a padding oracle that could be used to decrypt data. In order for this to be exploitable "non-stitched" ciphersuites must be in use. Stitched ciphersuites are optimised implementations of certain commonly used ciphersuites. Also the application must call SSL_shutdown() twice even if a protocol error has occurred (applications should not do this but some do anyway). Fixed in OpenSSL 1.0.2r (Affected 1.0.2-1.0.2q). Weakness: CWE-203 (Observable Discrepancy) ## Which versions are affected by CVE-2019-1559? It affects 82 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `openssl` | Red Hat:enterprise_linux:6::client | All versions | 0:1.0.1e-58.el6_10 | | `openssl-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:1.0.1e-58.el6_10 | | `openssl-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:1.0.1e-58.el6_10 | | `openssl-perl` | Red Hat:enterprise_linux:6::client | All versions | 0:1.0.1e-58.el6_10 | | `openssl-static` | Red Hat:enterprise_linux:6::client | All versions | 0:1.0.1e-58.el6_10 | | `openssl` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.0.1e-58.el6_10 | | `openssl-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.0.1e-58.el6_10 | | `openssl-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.0.1e-58.el6_10 | | `openssl-perl` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.0.1e-58.el6_10 | | `openssl-static` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.0.1e-58.el6_10 | | `openssl` | Red Hat:enterprise_linux:6::server | All versions | 0:1.0.1e-58.el6_10 | | `openssl-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:1.0.1e-58.el6_10 | | `openssl-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:1.0.1e-58.el6_10 | | `openssl-perl` | Red Hat:enterprise_linux:6::server | All versions | 0:1.0.1e-58.el6_10 | | `openssl-static` | Red Hat:enterprise_linux:6::server | All versions | 0:1.0.1e-58.el6_10 | | `openssl` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.0.1e-58.el6_10 | | `openssl-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.0.1e-58.el6_10 | | `openssl-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.0.1e-58.el6_10 | | `openssl-perl` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.0.1e-58.el6_10 | | `openssl-static` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.0.1e-58.el6_10 | | `openssl` | SUSE:Enterprise Storage 4 | All versions | 1.0.2j-60.49.1 | | `compat-openssl098` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 0.9.8j-106.12.1 | | `openssl` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 1.0.2j-60.49.1 | | `compat-openssl098` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 0.9.8j-106.12.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 1.0.2p-3.6.1 | | `compat-openssl098` | SUSE:Linux Enterprise Module for Legacy 12 | All versions | 0.9.8j-106.12.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise Module for Legacy 15 | All versions | 1.0.2p-3.14.2 | | `openssl` | SUSE:Linux Enterprise Point of Sale 11 SP3 | All versions | 0.9.8j-0.106.21.1 | | `openssl` | SUSE:Linux Enterprise Server 11 SP4-LTSS | All versions | 0.9.8j-0.106.21.1 | | `openssl1` | SUSE:Linux Enterprise Server 11-SECURITY | All versions | 1.0.1g-0.58.18.1 | | `openssl` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 1.0.1i-54.26.1 | | `openssl` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 1.0.2j-60.49.1 | | `openssl` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 1.0.2j-60.49.1 | | `openssl` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 1.0.2j-60.49.1 | | `openssl-1_0_0` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 1.0.2p-3.6.1 | | `compat-openssl098` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 0.9.8j-106.12.1 | | `openssl` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.0.1i-54.26.1 | | `compat-openssl098` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 0.9.8j-106.12.1 | | `openssl` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.0.2j-60.49.1 | | `compat-openssl098` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 0.9.8j-106.12.1 | Products: Canonical Ubuntu Linux, Debian Debian Linux, F5 Big-Ip Access Policy Manager, F5 Big-Ip Advanced Firewall Manager, F5 Big-Ip Analytics, F5 Big-Ip Application Acceleration Manager, F5 Big-Ip Application Security Manager, F5 Big-Ip Domain Name System, F5 Big-Ip Edge Gateway, F5 Big-Ip Fraud Protection Service, F5 Big-Ip Global Traffic Manager, F5 Big-Ip Link Controller, F5 Big-Ip Local Traffic Manager, F5 Big-Ip Policy Enforcement Manager, F5 Big-Ip Webaccelerator, F5 Big-Iq Centralized Management, F5 Traffix Signaling Delivery Controller, Fedoraproject Fedora, Mcafee Agent, Mcafee Data Exchange Layer and 62 more. ## How do I fix CVE-2019-1559? Upgrade to a fixed version. ## Is CVE-2019-1559 being exploited? There is no known exploitation of CVE-2019-1559 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild) - [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-1559 and fix it if it is affected. What it is: CVE-2019-1559 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 27 Feb 2019. 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-2019-1559 in the wild and no public exploit code. Affected product: Canonical Ubuntu Linux. 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-2019-1559/ (Markdown: https://insights.sbomify.com/CVE-2019-1559/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1559 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1559 - OSV: https://osv.dev/vulnerability/CVE-2019-1559 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-1559/ Summaries are generated and may contain mistakes; the official description above is the record.