CVE-2025-53634
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-07-10

Last updated on: 2025-08-14

Assigner: GitHub, Inc.

Description
Chall-Manager is a platform-agnostic system able to start Challenges on Demand of a player. The HTTP Gateway processes headers, but with no timeout set. With a slow loris attack, an attacker could cause Denial of Service (DoS). Exploitation does not require authentication nor authorization, so anyone can exploit it. It should nonetheless not be exploitable as it is highly recommended to bury Chall-Manager deep within the infrastructure due to its large capabilities, so no users could reach the system. Patch has been implemented by commit 1385bd8 and shipped in v0.1.4.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-07-10
Last Modified
2025-08-14
Generated
2026-05-07
AI Q&A
2025-07-10
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
ctfer-io chall-manager to 0.1.4 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 exists in Chall-Manager's HTTP Gateway, which processes headers without setting a timeout. An attacker can exploit this by performing a slow loris attack, where they send partial HTTP requests slowly to keep connections open, causing a Denial of Service (DoS). Exploitation does not require any authentication or authorization, meaning anyone can exploit it if they can reach the system. However, it is recommended to place Chall-Manager deep within the infrastructure to prevent direct access.


How can this vulnerability impact me? :

The vulnerability can lead to a Denial of Service (DoS) condition, making the Chall-Manager system unavailable by exhausting its resources through slow loris attacks. This can disrupt services relying on Chall-Manager, potentially causing downtime or degraded performance.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include ensuring that Chall-Manager is not exposed directly to users by burying it deep within the infrastructure, limiting access to trusted internal networks only. Additionally, update Chall-Manager to version 0.1.4 or later, which includes the patch for this vulnerability (commit 1385bd8).


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart