Skip to main content
CVE-2024-57641VulnerabilityPublished Updated

CVE-2024-57641: virtuoso-opensource · n/a

Affects virtuoso-opensourceSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

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

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 2026-10-26.

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. Immediately restrict network access to the Virtuoso OpenSource database service by implementing firewall rules or network segmentation to limit exposure to trusted hosts only. 2. Deploy Web Application Firewalls (WAFs) or SQL query inspection tools that can detect and block anomalous or malformed SQL queries targeting the sqlexp component. 3. Monitor database logs and network traffic for unusual SQL statements or patterns that could indicate exploitation attempts, enabling early detection and response. 4. Disable or limit remote SQL query execution capabilities if not required by the application environment. 5. Engage with OpenLink support or community forums to track the release of official patches or updates addressing this vulnerability and plan for immediate deployment once available. 6. Consider implementing rate limiting or connection throttling to reduce the impact of potential DoS attempts. 7. If feasible, evaluate upgrading to a later, unaffected version of Virtuoso or alternative database solutions until a patch is released. 8. Conduct internal penetration testing and vulnerability scanning focused on SQL injection vectors to identify and remediate other potential weaknesses in the environment.

Description

An issue in the sqlexp 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…