CVE-2025-61018
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue in the sqlo_place_dt_set component of openlink virtuoso-opensource v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA denial of service vulnerability exists in the sqlo_place_dt_set component of OpenLink Virtuoso Open-Source Edition v7.2.11. The vulnerability is triggered by specially crafted SQL statements, likely through malformed date/time values that cause the component to enter an error state, consume excessive resources, or crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed virtuoso-opensource versionRun 'virtuoso-t -?V' or check the package manager for the installed version of virtuoso-opensourceAffected if The installed version is exactly v7.2.11 or falls within the v7.2.x range prior to any patch
-
Confirm the SQL server component is runningCheck if the Virtuoso SQL server process (virtuoso-t or virtuoso-i) is actively listening on its configured SQL port (default 1111)Affected if The SQL server is running and accessible, exposing the sqlo_place_dt_set component to incoming SQL queries
-
Verify SQL execution is available to network clientsExamine the Virtuoso INI configuration file (virtuoso.ini) for 'ServerPort' or 'SQLServer' settings, and check if the service is bound to a network interface rather than localhost onlyAffected if The SQL service is bound to a non-loopback interface and accepts remote connections
-
Assess SQL privilege controlsReview the SQL user accounts and their privileges, particularly checking if untrusted users have permission to execute arbitrary SQL statementsAffected if Users with low or no privilege restrictions can submit custom SQL queries to the server
-
Check for recent security updates or patchesConsult the openlink virtuoso-opensource release notes or changelog to determine if a post-v7.2.11 patch has been appliedAffected if The installation remains at v7.2.11 with no subsequent security patch applied
A user is affected if the installed virtuoso-opensource is version 7.2.11 (or an unpatched earlier v7.2.x version) and the SQL server component with sqlo_place_dt_set is accessible to users who can submit specially crafted SQL statements.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor patches if available; otherwise, restrict SQL execution privileges and monitor database query patterns for abnormally long-running or resource-intensive statements targeting date/time operations.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61018 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-61018 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data