Skip to main content
Public proof of conceptFix available

CVE-2023-25076

A public proof of concept exists; no exploitation attested.

  • Published2023-03-30
  • WeaknessCWE-120

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A buffer overflow vulnerability exists in the handling of wildcard backend hosts of SNIProxy 0.6.0-2 and the master branch (commit: 822bb80df9b7b345cc9eba55df74a07b498819ba). A specially crafted HTTP or TLS packet can lead to arbitrary code execution. An attacker could send a malicious packet to trigger this vulnerability.

Timeline

dates in UTC
  1. 2023-03-3015:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-11-04 09:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-25076?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-25076?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Sniproxy project sniproxy
BranchAffectedFixed in
0.6= 0.6.0-2no fix published
0.6= 0.6.1no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As talos, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • SNIProxy
    Affected
    • = 0.6.0-2no fix stated
    • = Master 822bb80df9b7b345cc9eba55df74a07b498819bano fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2023-05-27

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • sniproxyUbuntu:Pro:18.04:LTSall versions · fixed in 0.5.0-2ubuntu0.1~esm1
  • sniproxyUbuntu:24.04:LTSall versions · fixed in 0.6.0-2.1build2
  • sniproxyUbuntu:22.04:LTSall versions · fixed in 0.6.0-2ubuntu0.22.04.1
  • sniproxyUbuntu:20.04:LTSall versions · fixed in 0.6.0-1ubuntu0.1
  • sniproxyMageia:8all versions · fixed in 0.6.1-1.mga8
  • sniproxyDebian:14all versions · fixed in 0.6.0-2.1
  • sniproxyDebian:13all versions · fixed in 0.6.0-2.1
  • sniproxyDebian:12all versions · fixed in 0.6.0-2.1

2 more package ranges on OSV.dev

Full record on NVD

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2023-03-30
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-fhgm-rvpq-xwx9

Frequently asked questions

What is CVE-2023-25076?

A buffer overflow vulnerability exists in the handling of wildcard backend hosts of SNIProxy 0.6.0-2 and the master branch (commit: 822bb80df9b7b345cc9eba55df74a07b498819ba). A specially crafted HTTP or TLS packet can lead to arbitrary code execution. An attacker could send a malicious packet to trigger this vulnerability.

Is CVE-2023-25076 actively exploited?

A proof-of-concept exploit exists for CVE-2023-25076, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2023-25076?

CVE-2023-25076 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running sniproxy? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record