CVE-2025-48879
BaseFortify
Publication date: 2025-06-10
Last updated on: 2025-08-12
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| octoprint | octoprint | to 1.11.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-835 | The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. |
| CWE-140 | The product does not neutralize or incorrectly neutralizes delimiters. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-48879 is a denial of service (DoS) vulnerability in OctoPrint versions up to 1.11.1. It occurs because the server's multipart/form-data request handler gets stuck in an infinite loop when processing a malformed multipart/form-data request that lacks the required end boundary. Since the underlying Tornado web server is single-threaded, this infinite loop blocks the entire web server, making OctoPrint unresponsive to all requests. [1]
How can this vulnerability impact me? :
This vulnerability can cause the OctoPrint web server to become completely unresponsive, resulting in a denial of service. An unauthenticated attacker can exploit this by sending a specially crafted malformed multipart/form-data request, which causes the server to enter an endless loop and block all other operations. This can disrupt normal use of OctoPrint, potentially halting 3D printing management and monitoring until the server is restarted or patched. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unresponsive behavior or denial of service symptoms on the OctoPrint web server when it receives malformed multipart/form-data HTTP requests missing the required end boundary. Since the issue is triggered by a broken multipart/form-data request, you can attempt to reproduce the issue by sending a crafted HTTP request lacking the final boundary to OctoPrint endpoints handled by UploadStorageFallbackHandler. For detection, you might use tools like curl or netcat to send such malformed requests and observe if the server becomes unresponsive. For example, a curl command sending a multipart/form-data request without the final boundary could be constructed, but specific commands are not provided in the resources. Additionally, monitoring server responsiveness and logs for HTTP 400 errors after patching can help detect attempts to exploit this vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include upgrading OctoPrint to version 1.11.2 or later, where the vulnerability has been patched. The patch ensures that malformed multipart/form-data requests missing the final boundary are detected and responded to with an HTTP 400 Bad Request error, preventing the server from entering an infinite loop. Additionally, administrators are advised not to expose OctoPrint instances to hostile networks such as the internet, regardless of patch status, to reduce the attack surface. [1]