Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 3.84% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2019
CVE-2019-1563High confidence
Padding Oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey
OpenSSL · OpenSSL
3.7LowCVSS 3.1
Scheduled
Patch availableLow technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityLow→Operational priority:Low, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs OpenSSL OpenSSL and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
7 package statesRelease-specific package status
Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · main | openssl | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.1.1d-r1 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.22v3.22 · main | openssl | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.1.1d-r1 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.21v3.21 · main | openssl | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.1.1d-r1 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Debian trixietrixie · source | openssl | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.1.1d-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | openssl | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.1.1d-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | openssl | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.1.1d-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | openssl | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.1.1d-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
Direct vendor intelligence
0 current · 1 archivedAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2019-1563 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityopenssl: information disclosure in PKCS7_dataDecode and CMS_decrypt_set1_pkeyNo longer in the provider’s current catalogue
The vendor explicitly identifies these products as affected by this CVE.
- openssl.src as a component of Red Hat Enterprise Linux 5
- openssl as a component of Red Hat Enterprise Linux 6
- openssl-devel as a component of Red Hat Enterprise Linux 6
- openssl-perl as a component of Red Hat Enterprise Linux 6
- openssl-static as a component of Red Hat Enterprise Linux 6
- openssl.src as a component of Red Hat Enterprise Linux 6
- openssl as a component of Red Hat Enterprise Linux 7
- openssl-devel as a component of Red Hat Enterprise Linux 7
- openssl-libs as a component of Red Hat Enterprise Linux 7
- openssl-perl as a component of Red Hat Enterprise Linux 7
- openssl-static as a component of Red Hat Enterprise Linux 7
- openssl.src as a component of Red Hat Enterprise Linux 7
- Summary
- In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).
- Remediation
- Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).
What
In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).
Why
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).
Why
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Observable Discrepancy → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-203 ↗
CWE-203: Observable Discrepancy. The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Action
- Apply the fixed release for the affected product branch as recorded by Red Hat Product Security. Validate the exact product and build in the linked advisory before deployment.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 10 Sept 2019 · Last source change 17 Sept 2024, 01:11 UTC · CWE-203 · Observable Discrepancy
CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source FIRST · tracked since 2026-09-01
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2019-10120
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2019-1563 to advisory no longer present in the provider's current catalogue.Red Hat Product Security ↗
- Before
- remediation: access.redhat.com/CVE-2019-1563
- After
- advisory no longer present in the provider's current catalogue
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c); Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k); Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s) · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c); Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k); Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s) · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
- Remediation statusRemediation status changed from Awaiting fix to Patch available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Patch available
- ENISA EUVD mappingEUVD-2019-10120 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2019-10120"}
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: openssl.org/20190910.txt; removed vendor advisory: debian.org/dsa-4539; removed vendor advisory: debian.org/dsa-4540; 10 further removals.openssl.org ↗
- Before
- vendor advisory: debian.org/dsa-4539 · vendor advisory: debian.org/dsa-4540 · vendor advisory: lists.fedoraproject.org/GY6SNRJP2S7Y42GIIDO3HXPNMDYN2U3A · 9 more references
- After
- vendor advisory: openssl.org/20190910.txt
- SeveritySeverity changed from Unknown to Low.NIST NVD ↗
- Before
- Unknown
- After
- Low
- CVSS scoreCVSS score changed from not recorded to 3.7 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N).NIST NVD ↗
- Before
- not recorded
- After
- 3.7 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.