Skip to main content
VulnerabilityPublished Updated

CVE-2024-57642: 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, 12:54 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-57642, organizations should immediately restrict network access to Virtuoso database instances, ensuring they are not publicly accessible unless absolutely necessary. Employ network-level controls such as firewalls and VPNs to limit exposure. Monitor database logs and network traffic for anomalous or unusually crafted SQL queries that could indicate exploitation attempts. Implement rate limiting or query throttling if supported by the platform to reduce the risk of DoS conditions. Stay informed on vendor advisories and apply patches or updates as soon as they become available. Consider deploying Web Application Firewalls (WAFs) or database activity monitoring tools that can detect and block SQL injection patterns. Additionally, conduct regular security assessments and penetration tests focused on database components to identify and remediate similar injection vulnerabilities proactively.

Description

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