Skip to content
Noroxi
NVD / CVE Program· CNA hackerone

CVE-2023-28321: An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as…

MediumCVSS 5.9 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 24/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. Special conditions such as timing or configuration are required.
  • Fixed version: azl3 tensorflow 2.11.1-1 on Azure Linux 3.0 2.16.1-1; azl3 tensorflow 2.16.1-1 on Azure Linux 3.0 2.16.1-1; cbl2 curl 8.2.1-1 on CBL Mariner 2.0 8.2.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to azl3 tensorflow 2.11.1-1 on Azure Linux 3.0 2.16.1-1; azl3 tensorflow 2.16.1-1 on Azure Linux 3.0 2.16.1-1; cbl2 curl 8.2.1-1 on CBL Mariner 2.0 8.2.1-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

An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provided by a TLS library. This private wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before used for certificate checks. Puny coded names always start with `xn--` and should not be allowed to pattern match, but the wildcard check in curl could still check for `x*`, which would match even though the IDN name most likely contained nothing even resembling an `x`.

Published
May 26, 2023
Updated
Oct 23, 2026
EPSS
1.8% · 78th percentile

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.8%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.9
CNA · hackerone
5.9
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2023-28321

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Check your site's encryptionRun the SSL check

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Check your site's encryptionRun 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.

VendorProduct
haxxcurl
debiandebian linux
fedoraprojectfedora
netappclustered data ontap
netappontap antivirus connector
netapph300s firmware
netapph300s
netapph500s firmware
netapph500s
netapph700s firmware
netapph700s
netapph410s firmware

and 2 more

Check your site's encryption

This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.

Run the SSL check

Versions reported by the vendor

Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

  • n/a https://github.com/curl/curl

    • Fixed in 8.1.0affected

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:8curlbefore 7.61.1-30.el8_8.37.61.1-30.el8_8.3
AlmaLinux:8libcurlbefore 7.61.1-30.el8_8.37.61.1-30.el8_8.3
AlmaLinux:8libcurl-develbefore 7.61.1-30.el8_8.37.61.1-30.el8_8.3
AlmaLinux:8libcurl-minimalbefore 7.61.1-30.el8_8.37.61.1-30.el8_8.3
AlmaLinux:9curlbefore 7.76.1-23.el9_2.27.76.1-23.el9_2.2
AlmaLinux:9curl-minimalbefore 7.76.1-23.el9_2.27.76.1-23.el9_2.2
AlmaLinux:9libcurlbefore 7.76.1-23.el9_2.27.76.1-23.el9_2.2
AlmaLinux:9libcurl-develbefore 7.76.1-23.el9_2.27.76.1-23.el9_2.2
AlmaLinux:9libcurl-minimalbefore 7.76.1-23.el9_2.27.76.1-23.el9_2.2
Alpine:v3.15curlbefore 8.1.0-r08.1.0-r0
Debian:10curlbefore 7.64.0-4+deb10u77.64.0-4+deb10u7
Debian:12curlbefore 7.88.1-107.88.1-10
openSUSE:Leap Micro 5.3curlbefore 8.0.1-150400.5.23.18.0.1-150400.5.23.1
openSUSE:Tumbleweedcurlbefore 8.1.0-1.18.1.0-1.1
Red Hat:enterprise_linux:8::baseoscurlbefore 0:7.61.1-30.el8_8.30:7.61.1-30.el8_8.3
Red Hat:enterprise_linux:8::baseoscurl-debuginfobefore 0:7.61.1-30.el8_8.30:7.61.1-30.el8_8.3
Red Hat:enterprise_linux:8::baseoscurl-debugsourcebefore 0:7.61.1-30.el8_8.30:7.61.1-30.el8_8.3
Red Hat:enterprise_linux:8::baseoscurl-minimal-debuginfobefore 0:7.61.1-30.el8_8.30:7.61.1-30.el8_8.3
Red Hat:enterprise_linux:8::baseoslibcurlbefore 0:7.61.1-30.el8_8.30:7.61.1-30.el8_8.3
Red Hat:enterprise_linux:8::baseoslibcurl-debuginfobefore 0:7.61.1-30.el8_8.30:7.61.1-30.el8_8.3
Red Hat:enterprise_linux:8::baseoslibcurl-develbefore 0:7.61.1-30.el8_8.30:7.61.1-30.el8_8.3
Red Hat:enterprise_linux:8::baseoslibcurl-minimalbefore 0:7.61.1-30.el8_8.30:7.61.1-30.el8_8.3
Red Hat:enterprise_linux:8::baseoslibcurl-minimal-debuginfobefore 0:7.61.1-30.el8_8.30:7.61.1-30.el8_8.3
Red Hat:enterprise_linux:9::appstreamcurl-debuginfobefore 0:7.76.1-23.el9_2.20:7.76.1-23.el9_2.2

+79

Same product

haxx: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-22901curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session…
    51Plan
  • CVE-2023-38039When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.
    47Plan
  • CVE-2024-2398HTTP/2 push headers memory-leak
    45Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-28319May 26, 2023 · A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH server's public key using a SHA…
    31Monitor
  • ← EarlierCVE-2023-28320May 26, 2023 · A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backends for resolving host names…
    24Monitor
  • Later →CVE-2023-28322May 26, 2023 · An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read…
    15Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 tensorflow 2.11.1-1 on Azure Linux 3.02.16.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 tensorflow 2.16.1-1 on Azure Linux 3.02.16.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 curl 8.2.1-1 on CBL Mariner 2.08.2.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 mysql 8.0.34-1 on CBL Mariner 2.08.0.34-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 rust 1.72.0-2 on CBL Mariner 2.01.72.0-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:curl7.76.1-23.el9_2.2 · AlmaLinux:9Package registry (OSV)
almalinux:curl-minimal7.76.1-23.el9_2.2 · AlmaLinux:9Package registry (OSV)
almalinux:libcurl7.76.1-23.el9_2.2 · AlmaLinux:9Package registry (OSV)
almalinux:libcurl-devel7.76.1-23.el9_2.2 · AlmaLinux:9Package registry (OSV)
almalinux:libcurl-minimal7.76.1-23.el9_2.2 · AlmaLinux:9Package registry (OSV)
alpine:curl8.1.0-r0 · Alpine:v3.15Package registry (OSV)
debian:curl7.88.1-10 · Debian:12Package registry (OSV)
opensuse:curl8.0.1-150400.5.23.1 · openSUSE:Leap Micro 5.3Package registry (OSV)
red hat:curl0:7.76.1-23.el9_2.2 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:curl-debuginfo0:7.76.1-23.el9_2.2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:curl-debugsource0:7.76.1-23.el9_2.2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:curl-minimal0:7.76.1-23.el9_2.2 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:curl-minimal-debuginfo0:7.76.1-23.el9_2.2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:jbcs-httpd24-apr0:1.7.0-8.el7jbcs · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-apr-debuginfo0:1.7.0-8.el7jbcs · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:libcurl0:7.76.1-23.el9_2.2 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:libcurl-debuginfo0:7.76.1-23.el9_2.2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:libcurl-devel0:7.76.1-23.el9_2.2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:libcurl-minimal0:7.76.1-23.el9_2.2 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:libcurl-minimal-debuginfo0:7.76.1-23.el9_2.2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:curl0:7.61.1-30.el8_8.3 · Rocky Linux:8Package registry (OSV)
suse:curl8.0.1-150400.5.23.1 · SUSE:Linux Enterprise Micro 5.3Package 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.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

nvd-primary

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

kotlin
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {  // Left empty for the test environment}

Fixed

kotlin
val client = OkHttpClient.Builder()  .certificatePinner(    CertificatePinner.Builder()      .add("api.sirius.example", "sha256/…")      .build()  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

References

All records