Quick answers
- Is CVE-2023-31717 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2023-31717 being exploited in the wild.
- How severe is CVE-2023-31717?
- Low severity, with a CVSS score of 3.1, published 22 September 2023.
- Which products and versions are affected?
- fuxa-server (npm) SEMVER:introduced=0,last_affected=1.1.12.
- Is there a fix for CVE-2023-31717?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2023-31717 attacked?
- It is attacked over the network.
- Am I affected by CVE-2023-31717?
- Check whether you run fuxa-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
FUXA versions up to 1.1.12 are vulnerable to SQL injection via the "id" parameter in HTTP POST requests with JSON-formatted bodies. The vulnerability exists because user-supplied input is not properly sanitized before being incorporated into SQL queries. An attacker with network access can craft malicious SQL payloads (such as time-based or data exfiltration queries) to extract data from the SQLite database without authentication. The attack is network-accessible and requires no user interaction. Patches are available in versions after 1.1.12.
Affected products
- FUXA FUXA <= 1.1.12
Identifiers
- CVE-2023-31717
- GHSA-v9q5-9crp-92f9
Timeline
- 2023-09-22: disclosed
- 2023-09-22: advisory: GitHub Security Advisory GHSA-v9q5-9crp-92f9 published