CVE-2025-0655: CVE-2025-0655: Rejected reason: ** REJECT ** DO NOT USE THIS CVE ID NUMBER. The Rejected CVE Record is a …
Unknown · · NVD published 2025-03-20 · posted 2025-02-05 · last modified 2025-04-15
What it is
Rejected reason: ** REJECT ** DO NOT USE THIS CVE ID NUMBER. The Rejected CVE Record is a duplicate of CVE-2024-55890. Notes: All CVE users should reference CVE-2024-55890 instead of this CVE Record. All references and descriptions in this candidate have been removed to prevent accidental usage.
| Weakness | Not specified |
|---|---|
| ATT&CK tactics | n/a |
Exploitation evidence
First exploit evidence seen: 2025-02-05 (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
Metasploit
exploit/linux/http/dtale_rce_cve_2025_0655: D-Tale RCE (disclosure 2025-02-05)
Sources: Rapid7 Metasploit Framework module metadata.
No ATT&CK techniques could be mapped or inferred for this CVE yet.
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.
Detection Generic guidance
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.