{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-52494 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-52494 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52494 is a high-severity denial of service vulnerability in n/a, published on 3 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-52494 and fix it if it is affected.\n\nWhat it is: CVE-2025-52494 is a high-severity denial of service vulnerability in n/a, published on 3 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-52494 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-52494/ (Markdown: https://insights.sbomify.com/CVE-2025-52494/index.md)","id":"CVE-2025-52494","markdown":"https://insights.sbomify.com/CVE-2025-52494/index.md","name":"CVE-2025-52494","record":{"aliases":["GHSA-pvqr-qr3w-3jpg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Ada Web Server","requires_auth":"none","summary":"An attacker can cause a denial of service in Ada Web Server by exhausting worker threads through malformed TLS handshakes that lack proper timeouts.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ada_web_server","vendor":"adacore"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Adacore Ada Web Server (AWS) before 25.2 is vulnerable to a denial-of-service (DoS) condition due to improper handling of SSL handshakes during connection initialization. When a client initiates an HTTPS connection, the server performs the SSL handshake before assigning the connection to a processing slot. However, there is no specific timeout set for this phase, and the server uses the default socket timeout, which is effectively infinite. An attacker can exploit this by sending a malformed TLS ClientHello message with incorrect length values. This causes the server to wait indefinitely for data that never arrives, blocking the worker thread (Line) handling the connection. By opening multiple such connections, up to the server's maximum limit, the attacker can exhaust all available working threads, preventing the server from handling new, legitimate requests.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Denial of service in n/a","id":"CVE-2025-52494","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Race condition in mbedtls","id":"CVE-2025-52496"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2025-52493"},"products":["n/a"],"published":"2025-09-03","related":[{"cvss_score":7.4,"headline":"Security feature bypass in n/a","id":"CVE-2024-55581","kev_date_added":null,"published":"2025-02-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-03","vendors":["n/a"]},"summary":"An attacker can cause a denial of service in Ada Web Server by exhausting worker threads through malformed TLS handshakes that lack proper timeouts.","url":"https://insights.sbomify.com/CVE-2025-52494/"}