Skip to main content
CVE-2024-37681VulnerabilityPublished Updated

CVE-2024-37681: 123 · n/a

Affects 123Source CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
6.5Medium
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:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 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

Affected software

ProductAffectedFixed in
GitHubdabaizhizhu/123pkg:github/dabaizhizhu/123Other threatsAffected
  • =1.0.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of an official patch, organizations should implement several practical mitigations: 1) Deploy network-level protections such as web application firewalls (WAFs) to detect and block abnormal or excessive requests targeting the index.html component. 2) Implement rate limiting on the management system’s web interface to prevent resource exhaustion from repeated requests. 3) Restrict network access to the management system by limiting exposure to trusted IP addresses or VPN-only access to reduce the attack surface. 4) Monitor system resource usage and logs for unusual spikes or patterns indicative of DoS attempts. 5) Engage with the vendor to obtain updates or patches and apply them promptly once available. 6) Consider deploying redundancy or failover mechanisms for critical management systems to maintain availability during attacks. 7) Conduct regular security assessments and penetration tests focused on resource exhaustion vulnerabilities to identify and remediate similar issues proactively.

Description

An issue the background management system of Shanxi Internet Chuangxiang Technology Co., Ltd v1.0.1 allows a remote attacker to cause a denial of service via the index.html component.

References

Community reviews

Loading reviews…