Skip to main content
CVE-2024-25656VulnerabilityPublished Updated

CVE-2024-25656: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Mar 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

To mitigate CVE-2024-25656, organizations should implement the following specific measures: 1) Apply any available patches or updates from AVSystem addressing input validation and data size limits during CPE registration as soon as they are released. 2) Implement strict input validation and size restrictions on registration data at the application and database layers to prevent excessive data storage. 3) Monitor registration logs and database usage patterns for abnormal spikes in data volume or unusual registration activity from unauthenticated devices. 4) Employ network-level controls such as rate limiting and filtering to restrict the number of registration attempts from individual or groups of CPE devices. 5) Segment the management platform network to isolate critical database components and reduce the blast radius of potential attacks. 6) Use anomaly detection and alerting systems to identify potential DDoS attempts targeting the registration process. 7) Engage with AVSystem support for guidance and best practices specific to the UMP deployment. These steps go beyond generic advice by focusing on proactive monitoring, network controls, and layered defenses tailored to the vulnerability's exploitation vector.

Description

Improper input validation in AVSystem Unified Management Platform (UMP) 23.07.0.16567~LTS can result in unauthenticated CPE (Customer Premises Equipment) devices storing arbitrarily large amounts of data during registration. This can potentially lead to DDoS attacks on the application database and, ultimately, affect the entire product.

References

Community reviews

Loading reviews…