Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-qcjq-7f7v-pvc8

HIGHFix: 0xJacky/nginx-ui@d70e37c

GHSA-qcjq-7f7v-pvc8 is a high-severity (CVSS 8.8) CWE-74 vulnerability in github.com/0xJacky/Nginx-UI. O3 Security confirms whether GHSA-qcjq-7f7v-pvc8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Nginx-UI vulnerable to authenticated RCE through injecting into the application config via CRLF

Also known asCVE-2024-23828GO-2024-2480
Published
Jan 29, 2024
Updated
Jul 6, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Real-World Exposure

1 pkg affected
🐹github.com/0xJacky/Nginx-UI

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Fix bypass to the following bugs

Allowing to inject directly in the app.ini via CRLF to change the value of test_config_cmd and start_cmd resulting in an Authenticated RCE

Impact

Authenticated Remote execution on the host

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/0xJacky/Nginx-UIall versions1.9.10-0.20240126104956-d70e37c8575e

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/0xJacky/Nginx-UI. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/0xJacky/Nginx-UI to 1.9.10-0.20240126104956-d70e37c8575e or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qcjq-7f7v-pvc8 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-qcjq-7f7v-pvc8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-qcjq-7f7v-pvc8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Fix bypass to the following bugs - https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-pxmr-q2x3-9x9m - https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-8r25-68wm-jw35 Allowing to inject directly in the `app.ini` via CRLF to change the value of `test_config_cmd` and `start_cmd` resulting in an Authenticated RCE ### Impact Authenticated Remote execution on the host
O3 Security · Impact-Aware SCA

Is GHSA-qcjq-7f7v-pvc8 in your dependencies?

O3 detects GHSA-qcjq-7f7v-pvc8 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.