BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2019
CVE-2019-18348High confidence

Affected product: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

Unknown · Unknown

6.1MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 3.51% 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.
  • Monitor vendor guidance and exploitation sources for a material change.

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: As exposure requiresRemediation target: Within 365 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.

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-2019-18348 · CSAF 2.0 · revision 60 · interimSUSE Product Security TeamCVE-2019-18348
78 known affected

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

  • python3 as component of HPE Helion OpenStack 8
  • python3-curses as component of HPE Helion OpenStack 8
  • python as component of SUSE CaaS Platform 4.0
  • python-curses as component of SUSE CaaS Platform 4.0
  • python-gdbm as component of SUSE CaaS Platform 4.0
  • python-tk as component of SUSE CaaS Platform 4.0
  • python as component of SUSE Enterprise Storage 6
  • python as component of SUSE Enterprise Storage 7
  • 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
  • python36 as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • python as component of SUSE Linux Enterprise High Performance Computing 15 SP1-LTSS
Summary
An issue was discovered in urllib2 in Python 2.x through 2.7.17 and urllib in Python 3.x through 3.8.0. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the host component of a URL) followed by an HTTP header. This is similar to the CVE-2019-9740 query string issue and the CVE-2019-9947 path string issue. (This is not exploitable when glibc has CVE-2016-10739 fixed.). This is fixed in: v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1; v3.6.11, v3.6.11rc1, v3.6.12; v3.7.8, v3.7.8rc1, v3.7.9; v3.8.3, v3.8.3rc1, v3.8.4, v3.8.4rc1, v3.8.5, v3.8.6, v3.8.6rc1.
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-2019-8136

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

An issue was discovered in urllib2 in Python 2.x through 2.7.17 and urllib in Python 3.x through 3.8.0. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the host component of a URL) followed by an HTTP header. This is similar to the CVE-2019-9740 query string issue and the CVE-2019-9947 path string issue. (This is not exploitable when glibc has CVE-2016-10739 fixed.). This is fixed in: v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1; v3.6.11, v3.6.11rc1, v3.6.12; v3.7.8, v3.7.8rc1, v3.7.9; v3.8.3, v3.8.3rc1, v3.8.4, v3.8.4rc1, v3.8.5, v3.8.6, v3.8.6rc1.

What

An issue was discovered in urllib2 in Python 2.x through 2.7.17 and urllib in Python 3.x through 3.8.0. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the host component of a URL) followed by an HTTP header. This is similar to the CVE-2019-9740 query string issue and the CVE-2019-9947 path string issue. (This is not exploitable when glibc has CVE-2016-10739 fixed.). This is fixed in: v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1; v3.6.11, v3.6.11rc1, v3.6.12; v3.7.8, v3.7.8rc1, v3.7.9; v3.8.3, v3.8.3rc1, v3.8.4, v3.8.4rc1, v3.8.5, v3.8.6, v3.8.6rc1.

Why

The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

An issue was discovered in urllib2 in Python 2.x through 2.7.17 and urllib in Python 3.x through 3.8.0. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the host component of a URL) followed by an HTTP header. This is similar to the CVE-2019-9740 query string issue and the CVE-2019-9947 path string issue. (This is not exploitable when glibc has CVE-2016-10739 fixed.). This is fixed in: v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1; v3.6.11, v3.6.11rc1, v3.6.12; v3.7.8, v3.7.8rc1, v3.7.9; v3.8.3, v3.8.3rc1, v3.8.4, v3.8.4rc1, v3.8.5, v3.8.6, v3.8.6rc1.

Why

The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

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.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-74 ↗

CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'). The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

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:R/S:C/C:L/I:L/A:N

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.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SChangedScope: The attack can affect a component governed by a different security authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
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.
NetworkUnauthenticatedCWE-74
A

Official authority intelligence

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

BSI · German · WID-SEC-2022-2191Python: Schwachstelle ermöglicht Manipulation von Dateien

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Python ausnutzen, um Dateien zu manipulieren.

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-1015Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2019-16056 Référence CVE CVE-2019-16168 https://www.cve.org/CVERecord?id=CVE-2019-16168 Référence CVE CVE-2019-16905 https://www.cve.org/CVERecord?id=CVE-2019-16905 Référence CVE CVE-2019-17498 https://www.cve.org/CVERecord?id=CVE-2019-17498 Référence CVE CVE-2019-17543 https://www.cve.org/CVERecord?id=CVE-2019-17543 Référence CVE CVE-2019-17594 https://www.cve.org/CVERecord?id=CVE-2019-17594 Référence CVE CVE-2019-17595 https://www.cve.org/CVERecord?id=CVE-2019-17595 Référence CVE CVE-2019-18224 https://www.cve.org/CVERecord?id=CVE-2019-18224 Référence CVE CVE-2019-18276 https://www.cve.org/CVERecord?id=CVE-2019-18276 Référence CVE CVE-2019-18348 https://www.cve.org/CVERecord?id=CVE-2019-18348 Référence CVE CVE-2019-19126 https://www.cve.org/CVERecord?id=CVE-2019-19126 Référence CVE CVE-2019-19242 https://www.cve.org/CVERecord?id=CVE-2019-19242 Référence CVE CVE-2019-19244 https://www.cve.org/CVERecord?id=CVE-2019-19244 Référence CVE CVE-2019-19317 https://www.cve.org/CVERecord?id=CVE-2019-19317 Référence CVE CVE-2019-19603 https://www.cve.org/CVERecord?id=CVE-2019-19603 Référence CVE CVE-2019-19645 https://www.cve.org/CVERecord?id=CVE-2019-19645 Référence CVE CVE-2019-19646 https://www.cve.org/CVERecord?id=CVE-2019-19646 Référence CVE CVE-2019-19880 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0513Multiples vulnérabilités dans les produits IBM

m.com/support/pages/node/7009301 Bulletin de sécurité IBM 7009987 du 06 juillet 2023 https://www.ibm.com/support/pages/node/7009987 Bulletin de sécurité IBM 7010095 du 06 juillet 2023 https://www.ibm.com/support/pages/node/7010095 Bulletin de sécurité IBM 7010099 du 06 juillet 2023 https://www.ibm.com/support/pages/node/7010099 Référence CVE CVE-2015-0254 https://www.cve.org/CVERecord?id=CVE-2015-0254 Référence CVE CVE-2015-20107 https://www.cve.org/CVERecord?id=CVE-2015-20107 Référence CVE CVE-2016-10735 https://www.cve.org/CVERecord?id=CVE-2016-10735 Référence CVE CVE-2018-20060 https://www.cve.org/CVERecord?id=CVE-2018-20060 Référence CVE CVE-2019-18348 https://www.cve.org/CVERecord?id=CVE-2019-18348 Référence CVE CVE-2019-8331 https://www.cve.org/CVERecord?id=CVE-2019-8331 Référence CVE CVE-2019-9740 https://www.cve.org/CVERecord?id=CVE-2019-9740 Référence CVE CVE-2020-26116 https://www.cve.org/CVERecord?id=CVE-2020-26116 Référence CVE CVE-2021-23336 https://www.cve.org/CVERecord?id=CVE-2021-23336 Référence CVE CVE-2021-28861 https://www.cve.org/CVERecord?id=CVE-2021-28861 Référence CVE CVE-2021-3733 https://www.cve.org/CVERecord?id=CVE-2021-3733 Référence CVE CVE-2021-3737 https://www.cve.org/CVERecord?id=CVE-2021-3737 Référence CVE CVE-2021-43138 https://www.cve.org/CVERecord?id=CVE-2021

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-928Multiples vulnérabilités dans les produits IBM

d?id=CVE-2018-25031 Référence CVE CVE-2018-3721 https://www.cve.org/CVERecord?id=CVE-2018-3721 Référence CVE CVE-2019-0205 https://www.cve.org/CVERecord?id=CVE-2019-0205 Référence CVE CVE-2019-1010266 https://www.cve.org/CVERecord?id=CVE-2019-1010266 Référence CVE CVE-2019-10172 https://www.cve.org/CVERecord?id=CVE-2019-10172 Référence CVE CVE-2019-10202 https://www.cve.org/CVERecord?id=CVE-2019-10202 Référence CVE CVE-2019-10744 https://www.cve.org/CVERecord?id=CVE-2019-10744 Référence CVE CVE-2019-11358 https://www.cve.org/CVERecord?id=CVE-2019-11358 Référence CVE CVE-2019-16935 https://www.cve.org/CVERecord?id=CVE-2019-16935 Référence CVE CVE-2019-18348 https://www.cve.org/CVERecord?id=CVE-2019-18348 Référence CVE CVE-2019-9636 https://www.cve.org/CVERecord?id=CVE-2019-9636 Référence CVE CVE-2019-9740 https://www.cve.org/CVERecord?id=CVE-2019-9740 Référence CVE CVE-2019-9947 https://www.cve.org/CVERecord?id=CVE-2019-9947 Référence CVE CVE-2020-11022 https://www.cve.org/CVERecord?id=CVE-2020-11022 Référence CVE CVE-2020-11023 https://www.cve.org/CVERecord?id=CVE-2020-11023 Référence CVE CVE-2020-13936 https://www.cve.org/CVERecord?id=CVE-2020-13936 Référence CVE CVE-2020-15523 https://www.cve.org/CVERecord?id=CVE-2020-15523 Référence CVE CVE-2020-26116 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2019-011323Python におけるインジェクションに関する脆弱性

Python には、インジェクションに関する脆弱性が存在します。 本脆弱性は、CVE-2019-9740 および CVE-2019-9947 と同様の脆弱性です。

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.
Patch available
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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 23 Oct 2019 · Last source change 5 Aug 2024, 01:54 UTC · CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

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-09-01
European sourceENISA EUVD · EUVD-2019-8136
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
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 ↗
  1. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    SUSE Product Security Team ↗
  2. ENISA EUVD mappingEUVD-2019-8136 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2019-8136"}
    ENISA EUVD ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: bugs.python.org/issue30458; removed vendor advisory: lists.fedoraproject.org/4X3HW5JRZ7GCPSR7UHJOLD7AWLTQCDVR; removed vendor advisory: lists.fedoraproject.org/A5NSAX4SC3V64PGZUPH7PRDLSON34Q5A; 6 further removals.
    Before
    vendor advisory: lists.fedoraproject.org/4X3HW5JRZ7GCPSR7UHJOLD7AWLTQCDVR · vendor advisory: lists.fedoraproject.org/A5NSAX4SC3V64PGZUPH7PRDLSON34Q5A · vendor advisory: lists.fedoraproject.org/JCPGLTTOBB3QEARDX4JOYURP6ELNNA2V · 5 more references
    After
    vendor advisory: bugs.python.org/issue30458
    bugs.python.org ↗
  4. SeveritySeverity changed from Unknown to Medium.
    Before
    Unknown
    After
    Medium
    NIST NVD ↗
  5. CVSS scoreCVSS score changed from not recorded to 6.1 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).
    Before
    not recorded
    After
    6.1 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N)
    NIST NVD ↗
  6. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Remediation guidance recorded
ENISA EUVD · EUVD-2019-8136↗SUSE Product Security Team security advisory↗Vendor advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
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-2019-18348 · cve.blacktree.nl