CVE-2025-53530
BaseFortify
Publication date: 2025-07-07
Last updated on: 2025-07-10
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wegia | wegia | to 3.3.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-770 | The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the WeGIA server occurs because it does not properly validate the length of the HTTP GET parameter 'errorstr'. Attackers can send excessively long 'errorstr' values (up to 8,142 characters), causing the server to consume excessive CPU and memory resources. This leads to high latency, timeouts, and read errors, making the server vulnerable to Denial of Service (DoS) attacks. [1]
How can this vulnerability impact me? :
The vulnerability can severely degrade or disrupt the availability of the WeGIA server by exhausting its CPU and memory resources. This results in increased latency, timeouts, and errors, potentially causing service outages or denial of service for legitimate users. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending an HTTP GET request with an excessively long `errorstr` parameter to the WeGIA server and observing the server's response and resource usage. For example, using curl to send a request with 8,000 'A' characters in the `errorstr` parameter can help detect if the server is vulnerable. A sample command is: curl -v "https://your-wegia-server/WeGIA?errorstr=$(python3 -c 'print("A"*8000)')". Additionally, load testing tools like `wrk` can be used to simulate multiple concurrent requests to observe timeouts and read errors indicating vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade the WeGIA server to version 3.3.0 or later, where the vulnerability is fixed by proper validation of the `errorstr` parameter length. Until the upgrade can be performed, consider implementing network-level protections such as rate limiting, web application firewalls (WAF) to block excessively long URLs or requests with large `errorstr` parameters, and monitoring for unusual spikes in CPU and memory usage that may indicate exploitation attempts. [1]