Skip to main content
CVE-2024-30870VulnerabilityPublished Updated

CVE-2024-30870: NS-ASG · n/a

Affects NS-ASGSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% 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:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Apr 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubhundanchen69/NS-ASGpkg:github/hundanchen69/NS-ASGOther threatsAffected
  • =6.3
Fixed in–

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

AI-suggested

1. Immediately restrict access to the /admin/address_interpret.php endpoint by implementing network-level controls such as IP whitelisting or VPN-only access to administrative interfaces. 2. Employ web application firewalls (WAFs) with custom rules to detect and block SQL Injection payloads targeting this endpoint. 3. Monitor database logs and application logs for unusual queries or error messages indicative of injection attempts. 4. Enforce the principle of least privilege on accounts accessing the NS-ASG management interface to minimize potential damage from compromised credentials. 5. Conduct thorough input validation and sanitization on all user inputs, especially those interacting with SQL queries, as a long-term fix. 6. Coordinate with netentsec for timely patch deployment once available and test patches in a controlled environment before production rollout. 7. Consider network segmentation to isolate management interfaces from general user networks. 8. Regularly update and audit security configurations to detect and remediate any exposure of administrative endpoints. 9. Educate administrators about the risks of SQL Injection and encourage vigilance for suspicious activity.

Description

netentsec NS-ASG 6.3 is vulnerable to SQL Injection via /admin/address_interpret.php.

References

Community reviews

Loading reviews…