BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2022
CVE-2022-40899High confidence

An issue discovered in Python Charmers Future 0.18.2 and earlier allows remote attackers to cause a denial of service via crafted Set-Cookie header from malicious web server

Unknown · Unknown

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 15 Apr 2025

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 1.87% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

1 package state
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian bookwormbookworm · sourcepython-futureAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Open-source package ranges1 source-attributed range

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
pipfuture<= 0.18.20.18.3GitHub advisory ↗github reviewed aggregator · 15 Apr 2025
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2022-40899 · CSAF 2.0 · revision 48 · interimSUSE Product Security TeamCVE-2022-40899
52 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • python-future as component of SUSE Enterprise Storage 6
  • python-future as component of SUSE Enterprise Storage 7
  • python3 as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • python3-curses as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • python-future as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • python3 as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • python3-curses as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • python-future as component of SUSE Linux Enterprise High Performance Computing Teradata 12 SP3
  • python3 as component of SUSE Linux Enterprise High Performance Computing Teradata 12 SP3
  • python3 as component of SUSE Linux Enterprise Server 12 SP2-BCL
  • python3-curses as component of SUSE Linux Enterprise Server 12 SP2-BCL
  • python-future as component of SUSE Linux Enterprise Server 12 SP4-ESPOS
Summary
An issue discovered in Python Charmers Future 0.18.2 and earlier allows remote attackers to cause a denial of service via crafted Set-Cookie header from malicious web server.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-0109

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

An issue discovered in Python Charmers Future 0.18.2 and earlier allows remote attackers to cause a denial of service via crafted Set-Cookie header from malicious web server.

What

An issue discovered in Python Charmers Future 0.18.2 and earlier allows remote attackers to cause a denial of service via crafted Set-Cookie header from malicious web server.

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

An issue discovered in Python Charmers Future 0.18.2 and earlier allows remote attackers to cause a denial of service via crafted Set-Cookie header from malicious web server.

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Uncontrolled Resource Consumption → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-400 ↗

CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of serviceCWE-400Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-0794Dell ECS: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell ECS ausnutzen, um seine Privilegien zu erweitern, beliebigen Programmcode mit Administratorrechten auszuführen, Informationen offenzulegen, Dateien zu manipulieren, einen Cross-Site-Scripting-Angriff durchzuführen, Sicherheitsvorkehrungen zu umgehen oder einen Denial of Service Zustand herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2023-2229Splunk Splunk Enterprise: Mehrere Schwachstellen

Ein entfernter, authentifizierter Angreifer kann mehrere Schwachstellen in Splunk Splunk Enterprise ausnutzen, um beliebigen Code auszuführen, einen 'Denial of Service'-Zustand zu verursachen, seine Privilegien zu erweitern und weitere, nicht spezifizierte Auswirkungen zu verursachen.

Official advisory ↗
BSI · German · WID-SEC-2023-0089Python: Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Python ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20221228Security Bulletin 28 Dec 2022

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 28 Dec 2022, published on 28 December 2022. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0670Multiples vulnérabilités dans Splunk Machine Learning Toolkit

tion des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Splunk SVD-2024-0801 du 12 août 2024 https://advisory.splunk.com/advisories/SVD-2024-0801 Référence CVE CVE-2020-28473 https://www.cve.org/CVERecord?id=CVE-2020-28473 Référence CVE CVE-2020-28975 https://www.cve.org/CVERecord?id=CVE-2020-28975 Référence CVE CVE-2021-34141 https://www.cve.org/CVERecord?id=CVE-2021-34141 Référence CVE CVE-2022-25882 https://www.cve.org/CVERecord?id=CVE-2022-25882 Référence CVE CVE-2022-31799 https://www.cve.org/CVERecord?id=CVE-2022-31799 Référence CVE CVE-2022-40897 https://www.cve.org/CVERecord?id=CVE-2022-40897 Référence CVE CVE-2022-40899 https://www.cve.org/CVERecord?id=CVE-2022-40899 Référence CVE CVE-2022-45907 https://www.cve.org/CVERecord?id=CVE-2022-45907 Référence CVE CVE-2023-25399 https://www.cve.org/CVERecord?id=CVE-2023-25399 Référence CVE CVE-2023-2800 https://www.cve.org/CVERecord?id=CVE-2023-2800 Référence CVE CVE-2023-37920 https://www.cve.org/CVERecord?id=CVE-2023-37920 Référence CVE CVE-2023-43804 https://www.cve.org/CVERecord?id=CVE-2023-43804 Référence CVE CVE-2023-45803 https://www.cve.org/CVERecord?id=CVE-2023-45803 Référence CVE CVE-2023-5678 https://www.cve.org/CVERecord?id=CVE-2023-5678 Référence CVE CVE-2023-6730 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0535Multiples vulnérabilités dans les produits Splunk

urité Splunk SVD-2024-0718 du 01 juillet 2024 https://advisory.splunk.com/advisories/SVD-2024-0718 Référence CVE CVE-2018-10237 https://www.cve.org/CVERecord?id=CVE-2018-10237 Référence CVE CVE-2020-8908 https://www.cve.org/CVERecord?id=CVE-2020-8908 Référence CVE CVE-2021-29425 https://www.cve.org/CVERecord?id=CVE-2021-29425 Référence CVE CVE-2022-36364 https://www.cve.org/CVERecord?id=CVE-2022-36364 Référence CVE CVE-2022-40896 https://www.cve.org/CVERecord?id=CVE-2022-40896 Référence CVE CVE-2022-40897 https://www.cve.org/CVERecord?id=CVE-2022-40897 Référence CVE CVE-2022-40898 https://www.cve.org/CVERecord?id=CVE-2022-40898 Référence CVE CVE-2022-40899 https://www.cve.org/CVERecord?id=CVE-2022-40899 Référence CVE CVE-2023-2976 https://www.cve.org/CVERecord?id=CVE-2023-2976 Référence CVE CVE-2023-32681 https://www.cve.org/CVERecord?id=CVE-2023-32681 Référence CVE CVE-2023-34453 https://www.cve.org/CVERecord?id=CVE-2023-34453 Référence CVE CVE-2023-34454 https://www.cve.org/CVERecord?id=CVE-2023-34454 Référence CVE CVE-2023-34455 https://www.cve.org/CVERecord?id=CVE-2023-34455 Référence CVE CVE-2023-35116 https://www.cve.org/CVERecord?id=CVE-2023-35116 Référence CVE CVE-2023-37276 https://www.cve.org/CVERecord?id=CVE-2023-37276 Référence CVE CVE-2023-37920 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0061Multiples vulnérabilités dans les produits Splunk

De multiples vulnérabilités ont été découvertes dans les produits Splunk . Certaines d'entre elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur, un contournement de la politique de sécurité et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0701Multiples vulnérabilités dans Splunk

d?id=CVE-2022-35260 Référence CVE CVE-2022-35737 https://www.cve.org/CVERecord?id=CVE-2022-35737 Référence CVE CVE-2022-36227 https://www.cve.org/CVERecord?id=CVE-2022-36227 Référence CVE CVE-2022-37599 https://www.cve.org/CVERecord?id=CVE-2022-37599 Référence CVE CVE-2022-37601 https://www.cve.org/CVERecord?id=CVE-2022-37601 Référence CVE CVE-2022-37603 https://www.cve.org/CVERecord?id=CVE-2022-37603 Référence CVE CVE-2022-38900 https://www.cve.org/CVERecord?id=CVE-2022-38900 Référence CVE CVE-2022-40023 https://www.cve.org/CVERecord?id=CVE-2022-40023 Référence CVE CVE-2022-40897 https://www.cve.org/CVERecord?id=CVE-2022-40897 Référence CVE CVE-2022-40899 https://www.cve.org/CVERecord?id=CVE-2022-40899 Référence CVE CVE-2022-41715 https://www.cve.org/CVERecord?id=CVE-2022-41715 Référence CVE CVE-2022-41716 https://www.cve.org/CVERecord?id=CVE-2022-41716 Référence CVE CVE-2022-41720 https://www.cve.org/CVERecord?id=CVE-2022-41720 Référence CVE CVE-2022-41722 https://www.cve.org/CVERecord?id=CVE-2022-41722 Référence CVE CVE-2022-42003 https://www.cve.org/CVERecord?id=CVE-2022-42003 Référence CVE CVE-2022-42004 https://www.cve.org/CVERecord?id=CVE-2022-42004 Référence CVE CVE-2022-42915 https://www.cve.org/CVERecord?id=CVE-2022-42915 Référence CVE CVE-2022-42916 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-003292Python Charmers Future における脆弱性

Python Charmers Future には、不特定の脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 22 Dec 2022 · Last source change 15 Apr 2025, 15:52 UTC · CWE-400 · Uncontrolled Resource Consumption

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-0109
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-40899 · cve.blacktree.nl