CVE-2021-47752
BaseFortify
Publication date: 2026-01-15
Last updated on: 2026-01-15
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sylkat | awebserver | 18 |
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 is a denial of service (DoS) issue in AWebServer GhostBuilding 18 that allows remote attackers to overwhelm the server by sending multiple concurrent HTTP requests. Attackers can target multiple endpoints, including /mysqladmin, to flood the server with high-volume requests, potentially causing it to crash or become unresponsive. [2]
How can this vulnerability impact me? :
The impact of this vulnerability is that an attacker can remotely crash or render the AWebServer GhostBuilding 18 service unresponsive by flooding it with numerous HTTP requests. This denial of service can disrupt availability, preventing legitimate users from accessing the server or its services. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unusually high volumes of concurrent HTTP requests to the server, especially targeting multiple endpoints including /mysqladmin. One approach is to use network monitoring tools or web server logs to identify such traffic patterns. While no specific detection commands are provided, using tools like 'netstat' to check for many concurrent connections or 'tcpdump' to capture HTTP traffic, filtering for requests to /mysqladmin, could help identify an attack. Additionally, analyzing web server access logs for repeated requests from the same IP or multiple threads could indicate exploitation attempts. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include limiting the number of concurrent HTTP requests allowed from a single client to prevent overwhelming the server. Implementing rate limiting or firewall rules to block or throttle excessive requests to sensitive endpoints like /mysqladmin can help. Additionally, monitoring and blocking suspicious IP addresses generating high-volume requests may reduce the impact. Since the vulnerability involves denial of service via request flooding, deploying web application firewalls (WAF) or using network-level protections to filter traffic can be effective. No official patches or updates are mentioned, so these defensive measures are recommended. [2]