GHSA-g7f6-rxc4-qhph: Pip/mesop vulnerability

Published Sep 23, 2026
·
Updated

Summary

The /csp endpoint accepts unauthenticated JSON reports and logs user-controlled values directly to stdout using print() without escaping control characters.

A remote attacker can include ANSI/VT100 escape sequences in fields such as blocked-uri or document-uri. When the logs are viewed in an ANSI-capable terminal, these sequences can manipulate the displayed output (e.g., clear the screen, hide text, or inject misleading messages), affecting the integrity of operator-facing logs.

Details

The CSP reporting endpoint accepts arbitrary JSON and prints several request fields directly:

mesop/server/staticfileserving.py python @app.route(prefixbaseurl("/csp"), methods=["POST"]) def cspreport(): report = request.getjson(force=True)

documenturi = report["csp-report"]["document-uri"] blockeduri = report["csp-report"]["blocked-uri"] violateddirective = report["csp-report"]["violated-directive"]

print(f"... Blocked URL: {blockeduri} ...")

Since these values are written to stdout without sanitization, ANSI escape sequences supplied by a remote client are preserved and interpreted by ANSI-compatible terminals.

PoC

Send the following request:

http POST /csp Content-Type: application/json

{ "csp-report": { "document-uri": "https://victim.example", "blocked-uri": "\u001b[2J\u001b[H\u001b[32m SECURITY OK - No CSP violations found \u001b[0m\n\u001b[8mhttps://evil.example", "violated-directive": "script-src-elem" } }

The request is accepted (HTTP 204), and the injected escape sequences are written to stdout unchanged.

When the captured output is rendered in a VT100-compatible terminal (verified using pyte), the original CSP warning is visually replaced with attacker-controlled content.

Expected output

text Content Security Policy Error

Directive: script-src-elem Blocked URL: ... App path: /app

Rendered output

text SECURITY OK - No CSP violations found https://evil.example App path: /app

Impact

An unauthenticated remote attacker can submit a crafted request to the /csp endpoint containing ANSI/VT100 escape sequences. Because these values are written directly to stdout without sanitization, an attacker can:

1. Inject forged log messages that appear to originate from the application. 2. Manipulate the terminal display by clearing the screen, moving the cursor, or overwriting previously displayed log output. 3. Hide or disguise security-relevant log entries using terminal formatting sequences such as colors, hidden text, or cursor positioning. 4. Mislead administrators during monitoring or incident response by displaying attacker-controlled messages (e.g., fake "SECURITY OK" notifications). 5. Reduce the integrity and trustworthiness of operator-facing logs, making troubleshooting and security investigations less reliable.

Affected Software

1 affected componentFixes available
pip/mesop<=1.3.3
1.3.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/mesop to a version that resolves this vulnerability.

    Fixed in 1.3.4

Event History

Sep 23, 2026
Advisory Published
via GitHub·07:01 PM
Data Sourced
via GitHub·07:01 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

Who is exposed to this issue?

Mesop deployments that expose the /__csp__ endpoint and whose stdout logs are viewed in an ANSI-capable terminal are exposed to log-display manipulation. The attacker can be remote because the endpoint accepts unauthenticated reports.

2

What does an attacker need to exploit it?

An attacker needs only to send a JSON POST to the CSP reporting endpoint containing ANSI/VT100 escape sequences in fields such as blocked-uri or document-uri. No authentication is required.

3

What is the practical impact?

The injected control sequences can alter how logs appear in a terminal, including clearing the screen, hiding text, or displaying misleading messages. This affects the integrity of operator-facing log output rather than the underlying logged data described here.

4

How can I tell whether my deployment is affected?

Check whether the application uses the shown CSP-report handler that prints document-uri, blocked-uri, or violated-directive directly to stdout without escaping control characters. Also confirm whether the /__csp__ endpoint is reachable by untrusted clients and logs are reviewed in ANSI-capable terminals.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203