CVE-2025-61025: An issue in the sslr_qst_get component of openlink virtuoso-opensource v7.2.11 allows attackers to cause a...
An issue in the sslr_qst_get 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
CVE-2025-61025 is a denial-of-service issue in OpenLink Virtuoso Open Source 7.2.11. A remote, unauthenticated attacker may be able to crash or exhaust the service using crafted SQL statements, affecting availability rather than data theft or tampering.
Executive priority
Treat this as a high availability risk for systems depending on Virtuoso. Prioritize internet-exposed or business-critical instances first. The evidence does not currently justify emergency exploitation assumptions, but the network-reachable, unauthenticated DoS profile warrants prompt containment and vendor tracking.
Technical view
The CVE describes a flaw in the sslr_qst_get component of virtuoso-opensource v7.2.11. CVSS 3.1 is 7.5: network reachable, low complexity, no privileges or user interaction, unchanged scope, and high availability impact only. Listed CWEs are CWE-400 and CWE-89.
Likely exposure
Organizations running OpenLink Virtuoso Open Source 7.2.11 are the likely exposure group, especially if SQL interfaces are reachable from untrusted networks. The CVE record lacks normalized vendor/product CPEs, so confirm exposure by asset inventory and installed version evidence.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The vulnerability is described as triggerable through crafted SQL statements, but public exploit maturity and patch status are not established in the provided sources.
Researcher notes
Evidence is thin: the CVE description names virtuoso-opensource v7.2.11 and sslr_qst_get, but affected CPE data is absent. No fix, workaround, exploit maturity, or active exploitation evidence is included. Avoid expanding scope beyond the named version without vendor confirmation.
Mitigation direction
Check OpenLink issue 1229 and vendor guidance for fixed versions or workarounds.
Restrict Virtuoso SQL access to trusted networks and authenticated users.
Place exposed instances behind firewall, VPN, or access-control layers.
Monitor for crashes, restarts, and unusual SQL error patterns.
Prioritize upgrade planning when an upstream fix is confirmed.
Validation and detection
Inventory Virtuoso deployments and confirm exact installed versions.
Identify whether SQL-facing services are exposed to untrusted networks.
Review service logs for repeated crashes or malformed SQL errors.
Track the GitHub issue and CVE record for patch updates.
Validate mitigations in non-production without using offensive payloads.
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 · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
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.