Skip to content

Werkzeug debugger vulnerable to remote execution when interacting with attacker controlled domain

High severity GitHub Reviewed Published May 5, 2024 in pallets/werkzeug • Updated Jun 14, 2024

Package

pip Werkzeug (pip)

Affected versions

< 3.0.3

Patched versions

3.0.3

Description

The debugger in affected versions of Werkzeug can allow an attacker to execute code on a developer's machine under some circumstances. This requires the attacker to get the developer to interact with a domain and subdomain they control, and enter the debugger PIN, but if they are successful it allows access to the debugger even if it is only running on localhost. This also requires the attacker to guess a URL in the developer's application that will trigger the debugger.

References

@davidism davidism published to pallets/werkzeug May 5, 2024
Published to the GitHub Advisory Database May 6, 2024
Reviewed May 6, 2024
Published by the National Vulnerability Database May 6, 2024
Last updated Jun 14, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.045%
(17th percentile)

Weaknesses

CVE ID

CVE-2024-34069

GHSA ID

GHSA-2g68-c3qc-8985

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.