CVE-2012-10058
BaseFortify
Publication date: 2025-08-13
Last updated on: 2025-08-14
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| rabidhamster | r4 | 1.25 |
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?
CVE-2012-10058 is a critical stack-based buffer overflow vulnerability in RabidHamster R4 version 1.25. It occurs due to unsafe use of the sprintf() function when logging malformed HTTP requests. A remote attacker can exploit this by sending a specially crafted HTTP request with a long URI, causing the buffer overflow during log entry generation. This overflow allows the attacker to overwrite the stack and execute arbitrary code with the privileges of the web server process. [1, 2, 3, 4]
How can this vulnerability impact me? :
This vulnerability can allow a remote attacker to execute arbitrary code on the affected server without any privileges or user interaction. This means the attacker can potentially take full control of the server process running RabidHamster R4, leading to unauthorized access, data compromise, denial of service, or further attacks within the network. [1, 2, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can be performed by sending an HTTP GET request to the server on port 8888 and checking the HTTP response header for the server string "R4 Embedded Server." This indicates the presence of the vulnerable RabidHamster R4 web server. For example, using curl: curl -I http://<target-ip>:8888/ and inspecting the Server header for "R4 Embedded Server" can help identify the vulnerable service. [1, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling the RabidHamster R4 HTTP service if it is not required, as it is disabled by default but may be enabled. Restrict network access to port 8888 to trusted hosts only to prevent remote exploitation. Since no patch or fix is available, consider removing or replacing the vulnerable RabidHamster R4 v1.25 server from your environment to eliminate the risk of exploitation. [3]