Executive Summary

This vulnerability exists in the time_t_to_dt component of openlink virtuoso-opensource version 7.2.11. It allows attackers to cause a Denial of Service (DoS) by crafting specific SQL statements that trigger a crash in the software.

The issue was identified when a fuzzer found that processing a particular SQL query involving a DATE column caused the application to crash. The crash occurs in the time_t_to_dt function when an invalid value is inserted into a DATE column, such as the value 72057594037927935 combined with a string '-675 seconds'.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can impact you by causing a Denial of Service (DoS) condition in the openlink virtuoso-opensource database server. An attacker can exploit this by sending specially crafted SQL statements that crash the server, potentially making the database unavailable to legitimate users.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by attempting to reproduce the crash condition using a specific SQL query that targets the time_t_to_dt function. A proof-of-concept (PoC) SQL script inserts an invalid value into a DATE column, which triggers the crash.

• Set up a Virtuoso 7.2.11 instance, for example using a Docker container.
• Run a test SQL query that inserts the value `72057594037927935` with a string `-675 seconds` into a DATE column.
• Observe if the system crashes or exhibits a Denial of Service behavior.

Useful 0 Not Useful 0

Compliance Impact

The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Useful 0 Not Useful 0

Mitigation Strategies

To mitigate the vulnerability in openlink virtuoso-opensource v7.2.11 related to the time_t_to_dt component causing a Denial of Service via crafted SQL statements, you should avoid running untrusted or crafted SQL queries that insert invalid or extreme values into DATE columns.

Additionally, consider isolating the Virtuoso instance in a controlled environment such as a Docker container to limit potential impact.

Monitor the official project repository or issue tracker for patches or updates addressing this issue and apply them as soon as they become available.

Useful 0 Not Useful 0