NULL dereference during PKCS7 data verification
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 78.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: OpenSSL OpenSSL 3.0.8.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to OpenSSL OpenSSL 3.0.8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initialization will fail. There is a missing check for the return value from the initialization function which later leads to invalid usage of the digest API most likely leading to a crash. The unavailability of an algorithm can be caused by using FIPS enabled configuration of providers or more commonly by not loading the legacy provider. PKCS7 data is processed by the SMIME library calls and also by the time stamp (TS) library calls. The TLS implementation in OpenSSL does not call these functions however third party applications would be affected if they call these functions to verify signatures on untrusted data.
- Published
- Feb 8, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.8% · 78th percentile
- CWE
- CWE-476
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
| stormshield | stormshield management center | cpe:2.3:a:stormshield:stormshield_management_center |
Check your server's TLS configuration
The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openssl openssl3.0.0 and later · up to 3.0.7 inclusive
- stormshield stormshield management centerbefore 3.3.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.
OpenSSL OpenSSL
- 3.0.0 and later · before 3.0.8affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | openssl | before 1:3.0.1-47.el9_1 | 1:3.0.1-47.el9_1 |
| AlmaLinux:9 | openssl-devel | before 1:3.0.1-47.el9_1 | 1:3.0.1-47.el9_1 |
| AlmaLinux:9 | openssl-libs | before 1:3.0.1-47.el9_1 | 1:3.0.1-47.el9_1 |
| AlmaLinux:9 | openssl-perl | before 1:3.0.1-47.el9_1 | 1:3.0.1-47.el9_1 |
| Alpine:v3.15 | openssl3 | before 3.0.8-r0 | 3.0.8-r0 |
| Alpine:v3.17 | openssl | from 3.0.0 · before 3.0.8-r0 | 3.0.8-r0 |
| crates.io | openssl-src | from 300.0.0 · before 300.0.12 | 300.0.12 |
| Debian:12 | openssl | before 3.0.8-1 | 3.0.8-1 |
| openSUSE:Leap 15.4 | openssl-3 | before 3.0.1-150400.4.17.1 | 3.0.1-150400.4.17.1 |
| openSUSE:Tumbleweed | openssl-3 | before 3.0.8-1.1 | 3.0.8-1.1 |
| Red Hat:enterprise_linux:9::appstream | openssl-debuginfo | before 1:3.0.1-47.el9_1 | 1:3.0.1-47.el9_1 |
| Red Hat:enterprise_linux:9::appstream | openssl-debugsource | before 1:3.0.1-47.el9_1 | 1:3.0.1-47.el9_1 |
| Red Hat:enterprise_linux:9::appstream | openssl-devel | before 1:3.0.1-47.el9_1 | 1:3.0.1-47.el9_1 |
| Red Hat:enterprise_linux:9::appstream | openssl-libs-debuginfo | before 1:3.0.1-47.el9_1 | 1:3.0.1-47.el9_1 |
| Red Hat:enterprise_linux:9::appstream | openssl-perl | before 1:3.0.1-47.el9_1 | 1:3.0.1-47.el9_1 |
| Red Hat:enterprise_linux:9::baseos | openssl | before 1:3.0.1-47.el9_1 | 1:3.0.1-47.el9_1 |
| Red Hat:enterprise_linux:9::baseos | openssl-libs | before 1:3.0.1-47.el9_1 | 1:3.0.1-47.el9_1 |
| Red Hat:rhel_eus:9.0::appstream | openssl-debuginfo | before 1:3.0.1-46.el9_0 | 1:3.0.1-46.el9_0 |
| Red Hat:rhel_eus:9.0::appstream | openssl-debugsource | before 1:3.0.1-46.el9_0 | 1:3.0.1-46.el9_0 |
| Red Hat:rhel_eus:9.0::appstream | openssl-devel | before 1:3.0.1-46.el9_0 | 1:3.0.1-46.el9_0 |
| Red Hat:rhel_eus:9.0::appstream | openssl-libs-debuginfo | before 1:3.0.1-46.el9_0 | 1:3.0.1-46.el9_0 |
| Red Hat:rhel_eus:9.0::appstream | openssl-perl | before 1:3.0.1-46.el9_0 | 1:3.0.1-46.el9_0 |
| Red Hat:rhel_eus:9.0::baseos | openssl | before 1:3.0.1-46.el9_0 | 1:3.0.1-46.el9_0 |
| Red Hat:rhel_eus:9.0::baseos | openssl-libs | before 1:3.0.1-46.el9_0 | 1:3.0.1-46.el9_0 |
+2
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code 65This week
Published before and after this one in the same product
- ← EarlierCVE-2023-0216Feb 8, 2023 · Invalid pointer dereference in d2i_PKCS7 functions31Monitor
- ← EarlierCVE-2023-0217Feb 8, 2023 · NULL dereference validating DSA public key31Monitor
- Later →CVE-2022-4304Feb 8, 2023 · Timing Oracle in RSA Decryption30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| OpenSSL OpenSSL | 3.0.8 | Vendor (CNA) |
| almalinux:openssl | 1:3.0.1-47.el9_1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:openssl-devel | 1:3.0.1-47.el9_1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:openssl-libs | 1:3.0.1-47.el9_1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:openssl-perl | 1:3.0.1-47.el9_1 · AlmaLinux:9 | Package registry (OSV) |
| alpine:openssl | 3.0.8-r0 · Alpine:v3.17 | Package registry (OSV) |
| alpine:openssl3 | 3.0.8-r0 · Alpine:v3.15 | Package registry (OSV) |
| crates.io:openssl-src | 300.0.12 | Package registry (OSV) |
| debian:openssl | 3.0.8-1 · Debian:12 | Package registry (OSV) |
| opensuse:openssl-3 | 3.0.1-150400.4.17.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:openssl | 1:3.0.1-47.el9_1 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:openssl-debuginfo | 1:3.0.1-47.el9_1 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-debugsource | 1:3.0.1-47.el9_1 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-devel | 1:3.0.1-47.el9_1 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-libs | 1:3.0.1-47.el9_1 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:openssl-libs-debuginfo | 1:3.0.1-47.el9_1 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-perl | 1:3.0.1-47.el9_1 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:openssl | 1:3.0.1-47.el9_1 · Rocky Linux:9 | Package registry (OSV) |
| suse:openssl-3 | 3.0.1-150400.4.17.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Hubert Kario (Red Hat)reporter
- Tomáš Mrázremediation developer
- Dmitry Belyavsky (Red Hat)reporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0067 · Feb 8, 2023(OpenSSL Güvenlik Güncellemesi )
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.