# CVE-2024-30868: SQL injection in n/a

> An attacker can perform SQL injection via the admin login page to read or modify data in the NS-ASG web application.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2024
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-ggj5-m92v-77xx

## What is CVE-2024-30868?

CVE-2024-30868 is a critical SQL injection vulnerability in n/a, published on 1 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-30868?

It affects 1 product.


Products: Netentsec Ns-Asg Firmware.

## How do I fix CVE-2024-30868?

No fix has been published for CVE-2024-30868 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-30868 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-30868 exists.

## Other vulnerabilities in n/a

- [CVE-2024-30858](https://insights.sbomify.com/CVE-2024-30858/): SQL injection in n/a (critical 9.8)
- [CVE-2024-30865](https://insights.sbomify.com/CVE-2024-30865/): SQL injection in n/a (critical 9.8)
- [CVE-2024-30867](https://insights.sbomify.com/CVE-2024-30867/): SQL injection in n/a (critical 9.8)
- [CVE-2024-30859](https://insights.sbomify.com/CVE-2024-30859/): SQL injection in n/a (high 8.8)
- [CVE-2024-30860](https://insights.sbomify.com/CVE-2024-30860/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-30868 and fix it if it is affected.

What it is: CVE-2024-30868 is a critical SQL injection vulnerability in n/a, published on 1 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-30868 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-30868/ (Markdown: https://insights.sbomify.com/CVE-2024-30868/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-30868
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-30868
- OSV: https://osv.dev/vulnerability/CVE-2024-30868

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-30868/
Summaries are generated and may contain mistakes; the official description above is the record.