CVE-2025-61028
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 time_t_to_dt 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 time_t_to_dt component of openlink virtuoso-opensource v7.2.11. Attackers can trigger the vulnerability by sending specially crafted SQL statements to the database, causing the service to become unavailable.
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 versionRun 'virtuoso-t -?V' from the Virtuoso installation directory, or connect to the database and execute 'select sys_stat('st_dbms_ver');' to retrieve the exact version stringAffected if Version is 7.2.11 or falls within the v7.2.x release line that includes the vulnerable datetime conversion component
-
Confirm SQL interface is network-accessibleCheck if the Virtuoso ISQL port (default 1111) or HTTP/WebDAV port (default 8890) is listening on a non-localhost interface using 'netstat -an | grep -E '1111|8890'' or similar network scanning toolsAffected if SQL or HTTP interface is exposed to network attackers (CVE is exploitable without authentication)
-
Verify datetime functions are accessible via SQLAttempt a simple datetime query such as 'SELECT NOW();' or 'SELECT CURRENT_TIMESTAMP;' through the ISQL command line or any SQL client connected to the Virtuoso instanceAffected if Datetime conversion functions are callable through SQL, which is the attack vector for this CVE
-
Monitor for service availability issuesAfter running datetime-heavy queries or if the service becomes unresponsive, check process status with 'ps aux | grep virtuoso' or check database connectivity with a simple SELECT queryAffected if Database service becomes unavailable or hangs when datetime conversion functions are invoked
Environment is affected if running Virtuoso Open-Source v7.2.x with network-accessible SQL interface where attackers can trigger the time_t_to_dt component via malicious datetime queries.
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 the vendor patch or upgrade to a patched version of virtuoso-opensource. If no patch is available, consider implementing SQL statement filtering or rate limiting as a temporary workaround.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61028 — 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-61028 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