CVE-2022-40468

Exp

Potential leak of left-over heap data if custom error page templates containing special non-standard variables are used. Tinyproxy commit 84f203f and earlier use uninitialized buffers in process_request() function.

Published: 2022-09-19 Last update: 2025-11-04 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-40468 is rated Exploit Available (58.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.17%). 2 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-40468

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-40468

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-26 0.15% 0.17% +0.02%
2 2026-02-19 0.19% 0.15% -0.05%
3 2026-02-18 — 0.19% —

Full EPSS history (17 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-40468

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2022-40468

OS Trackers for CVE-2022-40468

vendor priority summary link
alpine — CVE-2022-40468: 1 source package rows (tinyproxy); 19 state rows across 8 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 19, open 0. https://security.alpinelinux.org/vuln/CVE-2022-40468
debian not yet assigned CVE-2022-40468 not yet assigned priority: Debian including 1 source packages (tinyproxy), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-40468
gentoo low CVE-2022-40468: 1 GLSA(s) (202305-27), 1 atom(s) (net-proxy/tinyproxy); latest impact low. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-40468
suse high CVE-2022-40468 severity important: SUSE including 2 source package names (tinyproxy-1.11.1-2.1, tinyproxy-1.11.2-bp155.3.3.1), 3 product×package rows across 3 product lines (SUSE Package Hub 15 SP5, openSUSE Leap 15.5, openSUSE Tumbleweed): Fixed 3. https://www.suse.com/security/cve/CVE-2022-40468/
ubuntu medium CVE-2022-40468 medium priority: Ubuntu including 1 source packages (tinyproxy), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): released 6, not-affected 4, ignored 3. https://ubuntu.com/security/CVE-2022-40468

Affected software / configurations for CVE-2022-40468

Vendor Product Version Raw CPE
tinyproxy_project tinyproxy <= 1.11.1 cpe:2.3:a:tinyproxy_project:tinyproxy:*:*:*:*:*:*:*:*

References for CVE-2022-40468

cvelogic Threat Intelligence