# CVE-2023-24709: Code injection in n/a

> Attackers can cause a denial of service in Paradox IPR512 systems by exploiting code injection flaws in login parameters.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 21 Mar 2023
- **Updated:** 28 Feb 2025
- **Also known as:** GHSA-8fgr-w2w7-3965

## What is CVE-2023-24709?

CVE-2023-24709 is a high-severity code injection vulnerability in n/a, published on 21 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue found in Paradox Security Systems IPR512 allows attackers to cause a denial of service via the login.html and login.xml parameters.

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

## Which versions are affected by CVE-2023-24709?

It affects 1 product.


Products: Paradox Ipr512 Firmware.

## How do I fix CVE-2023-24709?

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

## Is CVE-2023-24709 being exploited?

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

Public exploit code:

- Paradox Security Systems IPR512 - Denial Of Service (exploitdb)
- In Paradox Security System IPR512 Web console login form page, attacker can input JavaScript string, such as "</script>" that will overwrite configurations in the file "login.xml" and cause the login page to crash.  (github_poc): https://github.com/darknesschieftain/Injection-vulnerability-in-Paradox-Security-Systems-IPR512-CVE-2023-24709-PoC

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-24709 and fix it if it is affected.

What it is: CVE-2023-24709 is a high-severity code injection vulnerability in n/a, published on 21 Mar 2023. 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-2023-24709 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-2023-24709/ (Markdown: https://insights.sbomify.com/CVE-2023-24709/index.md)
```

## Sources

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

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