Skip to content

OctoPrint Authenticated Reverse Proxy Page Authentication Bypass

Moderate severity GitHub Reviewed Published Apr 22, 2025 in OctoPrint/OctoPrint • Updated Apr 23, 2025

Package

pip octoprint (pip)

Affected versions

<= 1.10.3

Patched versions

1.11.0

Description

Impact

OctoPrint versions up until and including 1.10.3 contain a vulnerability that allows an attacker to bypass the login redirect and directly access the rendered HTML of certain frontend pages.

The impact on data exposure is minimal because, typically, data is loaded via API requests that correctly enforce user authentication. In the current codebase, cases where data is directly embedded in the page content are rare. However, one notable exception is the authenticated variant of the reverse proxy test page, which displays the IP addresses of configured reverse proxies.

The primary risk lies in potential future modifications to the codebase that might incorrectly rely on the vulnerable internal functions for authentication checks, leading to security vulnerabilities.

Patches

The vulnerability has been patched in version 1.11.0.

Details

An authentication bypass vulnerability exists in the following functions defined in octoprint/server/util/init.py:

  • require_login
  • require_login_with
  • require_fresh_login_with

By adding the HTTP header X-Preemptive-Recording: yes to HTTP requests, these functions allow requests to proceed without redirecting to the login screen, effectively bypassing the login mechanism in the frontend. However, this only grants access to frontend page content, while authenticated API endpoints still enforce proper session validation.

Credits

This vulnerability was discovered and responsibly disclosed to OctoPrint by Jacopo Tediosi

References

@foosel foosel published to OctoPrint/OctoPrint Apr 22, 2025
Published to the GitHub Advisory Database Apr 22, 2025
Reviewed Apr 22, 2025
Published by the National Vulnerability Database Apr 22, 2025
Last updated Apr 23, 2025

Severity

Moderate

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
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(6th percentile)

Weaknesses

CVE ID

CVE-2025-32788

GHSA ID

GHSA-qw93-h6pf-226x

Source code

Credits

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