Skip to main content
VulnerabilityPublished

CVE-2024-57637: virtuoso-opensource · SQL Injection

Affects virtuoso-opensourceSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 10:12 UTC

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

To mitigate CVE-2024-57637 effectively, organizations should implement several specific measures beyond generic advice: 1) Restrict network access to the Virtuoso database server by enforcing strict firewall rules and network segmentation, allowing only trusted hosts and applications to communicate with the database. 2) Deploy Web Application Firewalls (WAFs) or SQL query filtering mechanisms that can detect and block anomalous or suspicious SQL statements targeting the vulnerable component. 3) Enable detailed logging and monitoring of SQL queries to identify patterns indicative of exploitation attempts, such as repeated malformed or unusually complex queries. 4) Conduct thorough input validation and sanitization at the application layer to prevent malicious SQL from reaching the database engine. 5) Prepare for rapid patch deployment by closely monitoring OpenLink’s official channels for security updates or hotfixes addressing this vulnerability. 6) Consider temporary mitigation by upgrading to a non-vulnerable version if available or applying configuration changes that limit the functionality of the affected component. 7) Perform regular vulnerability assessments and penetration testing focused on SQL injection vectors to validate the effectiveness of implemented controls. 8) Educate development and operations teams about the risks of SQL injection and the importance of secure coding and database hardening practices.

Description

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