CVE-2025-61029: An issue in the sqlo_untry component of openlink virtuoso-opensource v7.2.11 allows attackers to cause a De...
An issue in the sqlo_untry component of openlink virtuoso-opensource v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements.
Security readout for executives and security teams
Plain-English summary
OpenLink Virtuoso Open Source 7.2.11 has a reported flaw that can let an unauthenticated network attacker crash or disable service using crafted SQL statements. The documented impact is availability loss, not data theft or code execution.
Executive priority
Prioritize exposed Virtuoso systems because the issue can interrupt service without authentication. Internal-only deployments are lower urgency but still need tracking until OpenLink confirms remediation details.
Technical view
The CVE describes a DoS issue in the sqlo_untry component of virtuoso-opensource v7.2.11. CVSS 3.1 is 7.5: network-accessible, low complexity, no privileges, no user interaction, unchanged scope, availability high. CWE-89 is assigned, but sources only state DoS impact.
Likely exposure
Exposure is most likely for organizations running OpenLink Virtuoso Open Source 7.2.11 with SQL access reachable from untrusted networks. The CVE affected-product metadata is incomplete, so inventory should rely on installed Virtuoso version and deployment role.
Exploitation context
The supplied data does not list this in CISA KEV, and no cited source confirms active exploitation. The CVSS vector indicates unauthenticated network reachability, so externally exposed services should be treated as higher urgency even without confirmed exploitation.
Researcher notes
Evidence is limited to the CVE record and linked GitHub issue. Do not assume broader affected versions, exploit availability, or a fixed release from the provided sources. The assigned CWE suggests SQL handling risk, but the stated security impact is DoS.
Mitigation direction
Check OpenLink issue 1228 and vendor advisories for confirmed fixed builds.
Restrict SQL service exposure to trusted networks only.
Place administrative or SQL interfaces behind VPN or equivalent access control.
Monitor for Virtuoso crashes, restarts, or unusual SQL error spikes.
Plan upgrade or configuration changes once vendor guidance is confirmed.
Validation and detection
Inventory all Virtuoso Open Source deployments and record exact versions.
Identify any v7.2.11 instances reachable from the internet or partner networks.
Review service logs for recent crashes tied to SQL statement handling.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.