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

> A local attacker can execute arbitrary code and read sensitive data via SQL injection in the loginid parameter of the Netcome NS-ASG Application Security Gateway.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2024
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-h8hf-rwc6-9296

## What is CVE-2024-28521?

CVE-2024-28521 is a high-severity SQL injection vulnerability in n/a, published on 21 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SQL Injection vulnerability in Netcome NS-ASG Application Security Gateway v.6.3.1 allows a local attacker to execute arbitrary code and obtain sensitive information via a crafted script to the loginid parameter of the /singlelogin.php component.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Netentsec Application Security Gateway Firmware.

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

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

## Is CVE-2024-28521 being exploited?

There is no known exploitation of CVE-2024-28521 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-7161](https://insights.sbomify.com/CVE-2023-7161/): Netentsec NS-ASG Application Security Gateway Login sql injection (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28521 is a high-severity SQL injection vulnerability in n/a, published on 21 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-28521 in the wild and no public exploit code.

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-28521/ (Markdown: https://insights.sbomify.com/CVE-2024-28521/index.md)
```

## Sources

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

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