Skip to main content
VulnerabilityPublished

CVE-2024-57661: virtuoso-opensource · Improper Resource Shutdown or Release

Affects virtuoso-opensourceSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 58% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubopenlink/virtuoso-opensourcepkg:github/openlink/virtuoso-opensourceOther threatsAffected
  • =7.2.11
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 targeting the sqlo_df component.
  3. Employ query whitelisting or input validation mechanisms where possible to detect and block suspicious SQL statements.
  4. Keep abreast of vendor advisories from OpenLink for patches or official workarounds and apply them promptly once available.
  5. Consider deploying rate limiting or connection throttling to reduce the risk of resource exhaustion from repeated malicious queries.
  6. If feasible, run Virtuoso OpenSource instances behind application-layer proxies or gateways that can filter and sanitize incoming requests.
  7. Regularly back up critical data and have incident response plans ready to restore service quickly in case of a successful DoS attack.
  8. Evaluate the necessity of exposing the database directly to the internet and disable or restrict remote access where not required.

Description

An issue in the sqlo_df component of openlink virtuoso-opensource v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements.

References

Community reviews

Loading reviews…