CVE-2024-57654: 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.7% chance of exploitation in 30 days – higher than 53% 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
Until an official patch is released, organizations should implement the following mitigations: 1) Restrict network access to the Virtuoso database server by using firewalls or network segmentation to limit exposure to trusted hosts only. 2) Employ intrusion detection and prevention systems (IDS/IPS) to monitor and block suspicious SQL queries or abnormal traffic patterns targeting the qst_vec_get_int64 function. 3) Disable or limit external query interfaces if not required, reducing the attack surface. 4) Monitor logs for unusual query activity that could indicate exploitation attempts. 5) Prepare for rapid patch deployment once a fix becomes available by maintaining up-to-date asset inventories and testing procedures. 6) Consider deploying rate limiting or query throttling mechanisms to mitigate the impact of potential DoS attempts. These steps go beyond generic advice by focusing on network-level controls and proactive monitoring specific to the nature of this vulnerability.
Description
An issue in the qst_vec_get_int64 component of openlink virtuoso-opensource v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements.