CVE-2025-55763
BaseFortify
Publication date: 2025-08-29
Last updated on: 2025-09-09
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| civetweb_project | civetweb | From 1.14 (inc) to 1.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-121 | A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a buffer overflow in the URI parser of CivetWeb versions 1.14 through 1.16. It occurs when the server processes a specially crafted HTTP request, causing a heap overflow that can crash the server or be exploited to execute arbitrary code remotely. [1]
How can this vulnerability impact me? :
An attacker can exploit this vulnerability to crash the CivetWeb server, causing a denial of service, or potentially execute arbitrary code remotely, which could lead to full system compromise. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending a specially crafted HTTP request to the CivetWeb server and observing if it crashes due to a heap overflow. A proof-of-concept (PoC) is available that demonstrates this by using a crafted input file. You can test it by running the command: `cat http_request_crash_input.txt | nc 127.0.0.1 8080`, which pipes the crafted HTTP request to the server and may trigger the vulnerability if present. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying the fix referenced in the pull request mentioned in the PoC repository. Until the fix is applied, you should consider restricting access to the CivetWeb server to trusted networks only, monitoring for crashes or unusual behavior, and avoiding exposure of the vulnerable versions (1.14 through 1.16) to untrusted networks. [1]