CVE-2024-57650: virtuoso-opensource · n/a
Affects virtuoso-opensourceSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubopenlink/virtuoso-opensourcepkg:github/openlink/virtuoso-opensourceOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Restrict network access to the Virtuoso OpenSource database instance by implementing firewall rules or network segmentation to limit exposure to trusted hosts only. 2. Monitor database logs and network traffic for unusual or malformed SQL queries that could indicate exploitation attempts targeting the qi_inst_state_free component. 3. Employ Web Application Firewalls (WAFs) or database activity monitoring tools capable of detecting and blocking suspicious SQL injection patterns. 4. Prepare for rapid deployment of patches or updates once the vendor releases a fix; subscribe to vendor advisories and CVE databases for updates. 5. Consider implementing rate limiting or query throttling to reduce the risk of resource exhaustion from crafted queries. 6. If possible, upgrade to a newer version of Virtuoso OpenSource that is not affected or apply vendor-recommended mitigations. 7. Conduct penetration testing and vulnerability assessments focused on SQL injection vectors in the database environment to identify and remediate similar weaknesses.
Description
An issue in the qi_inst_state_free component of openlink virtuoso-opensource v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements.