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

> Remote attackers can exploit SQL injection in JEPaaS to retrieve all database information via the login button log endpoint.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 15 Nov 2024
- **Updated:** 6 Jan 2025
- **Also known as:** GHSA-7q82-fxvh-gf2x

## What is CVE-2024-51164?

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

### Official description

Multiple parameters have SQL injection vulnerability in JEPaaS 7.2.8 via /je/login/btnLog/insertBtnLog, which could allow a remote user to submit a specially crafted query, allowing an attacker to retrieve all the information stored in the DB.

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

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

It affects 1 product.


Products: Ketr Jepaas.

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

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

## Is CVE-2024-51164 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-46535](https://insights.sbomify.com/CVE-2024-46535/): SQL injection in n/a (critical 9.8)
- [CVE-2024-51165](https://insights.sbomify.com/CVE-2024-51165/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51164 is a critical SQL injection vulnerability in n/a, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-51164 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-51164/ (Markdown: https://insights.sbomify.com/CVE-2024-51164/index.md)
```

## Sources

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

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