CVERadar
HIGH · CVSS 3.1 7.5Exploit-DBEPSS 3.65% (p90)Threat level 46

CVE-2024-0725: CVE-2024-0725: A vulnerability was found in ProSSHD 1.2 on Windows. It has been declared as problematic. …

prosshd · prosshd · NVD published 2024-01-20 · posted 2025-06-09 · last modified 2026-06-17

What it is

A vulnerability was found in ProSSHD 1.2 on Windows. It has been declared as problematic. This vulnerability affects unknown code. The manipulation leads to denial of service. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-251548.

WeaknessCWE-404
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (source: [email protected])
ATT&CK tacticsImpact

Exploitation evidence

First exploit evidence seen: 2025-06-09 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

Exploit-DB

  • EDB-52321: ProSSHD 1.2 20090726 - Denial of Service (DoS) (2025-06-09)

Sources: Exploit-DB (OffSec).

Defend the Chain

The attack chain for CVE-2024-0725 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.

Threat level 46/100
Defender level 1 · 0 XP
Chain links broken: 0/1

Pick a red technique card on the board, then choose the defence that stops it.

Defend against T1499 Endpoint Denial of Service Inferred

Inferred from description keywords

How to fix it

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

MITRE ATT&CK mitigations for this chain

  • M1037 Filter Network Traffic (for T1499) : Leverage services provided by Content Delivery Networks (CDN) or providers specializing in DoS mitigations to filter traffic upstream from services. Filter boundary traffic by blocking source addresses sourcing the attack, blocking ports that are being targeted, or blocking protocols being used for transport. To defend

Detection Generic guidance

  • Impact: Monitor service availability, unexpected encryption activity and mass file changes.

Response checklist Generic guidance

  1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
  2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
  3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
  4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Sources