NVD / CVE Program· CNA openssl

CVE-2018-0733: Incorrect CRYPTO_memcmp on HP-UX PA-RISC

MediumCVSS 5.9 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 25/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: 8.2% (FIRST EPSS); higher than 95% 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. Special conditions such as timing or configuration are required.
Fixed version: openssl (Alpine:v3.3) 1.0.2o-r0; openssl (Debian:12) 1.1.0h-1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to openssl (Alpine:v3.3) 1.0.2o-r0; openssl (Debian:12) 1.1.0h-1 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

Because of an implementation bug the PA-RISC CRYPTO_memcmp function is effectively reduced to only comparing the least significant bit of each byte. This allows an attacker to forge messages that would be considered as authenticated in an amount of tries lower than that guaranteed by the security claims of the scheme. The module can only be compiled by the HP-UX assembler, so that only HP-UX PA-RISC targets are affected. Fixed in OpenSSL 1.1.0h (Affected 1.1.0-1.1.0g).

Pre-auth

BDU:2019-01882

Published: Mar 27, 2018
Updated: Jun 16, 2026
EPSS: 8.2% · 95th percentile
CWE: —

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 23 / 40 · 5.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 2 / 30 · 8.2%

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.

Check your server's TLS configurationRun the SSL check

Is your version affected? Check it

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 help

Affected 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

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 check

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
- Fixed in OpenSSL 1.1.0h (Affected 1.1.0-1.1.0g)affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

openssl openssl1.1.0 and later · up to 1.1.0g inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Alpine:v3.3	openssl	from 1.1.0 · before 1.0.2o-r0	1.0.2o-r0
Debian:12	openssl	before 1.1.0h-1	1.1.0h-1

Same product

openssl: all records

Other 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…KEV
90Now
CVE-2021-3711SM2 Decryption Buffer Overflow
65This 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-2017-3737Dec 7, 2017 · OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state" mechanism.
47Plan
← EarlierCVE-2017-3738Dec 7, 2017 · There is an overflow bug in the AVX2 Montgomery multiplication procedure used in exponentiation with 1024-bit moduli.
27Monitor
Later →CVE-2018-0739Mar 27, 2018 · Constructed ASN.1 types with a recursive definition could exceed the stack
32Monitor

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
alpine:openssl	1.0.2o-r0 · Alpine:v3.3	Package registry (OSV)
debian:openssl	1.1.0h-1 · Debian:12	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.