Skip to content
VulniPulse
Sign in
Advisory severityMedium6.5Red Hat Linux

Medium [CVE-2025-61024] Denial of Service via crafted SQL statements in sqlo_try_in_loop

This medium-severity Red Hat Linux advisory covers CVE-2025-61024 affecting Red Hat Enterprise Linux 7, Red Hat package: virtuoso-opensource.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2025-61024 Source published Source updated

VulniPulse record published Record updated

CVE-2025-61024
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Summary

An issue in the sqlo_try_in_loop component of openlink virtuoso-opensource v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements. An attacker could send specially crafted SQL (Structured Query Language) statements to a specific component, `sqlo_try_in_loop`, leading to a Denial of Service (DoS).

This could make the service unavailable to legitimate users. Red Hat severity: Moderate — CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Weakness: CWE-606. Affected Red Hat products: Red Hat Enterprise Linux 7.

Will not fix / out of support: Red Hat Enterprise Linux 7. Red Hat does not currently list a fixing RHSA for this CVE.

Affected products named by the advisory: Red Hat package: virtuoso-opensource.

Is CVE-2025-61024 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2025-61024 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2025-61024?

The advisory VulniPulse tracks names no fixed release. Follow Red Hat's guidance for workarounds and updates.

Confirm against the vendor advisory before you patch.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists. Confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • To reduce the attack surface, restrict network access to the virtuoso-opensource service to only trusted clients using firewall rules. If the virtuoso-opensource service is not actively used, consider disabling it. To disable the service: `sudo systemctl stop virtuoso-opensource` `sudo systemctl disable virtuoso-opensource` Applying firewall rules to limit access to the service's port (e.g., 1111/tcp) from specific trusted IP addresses can also reduce exposure. `sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<TRUSTED_IP_ADDRESS>" port port="1111" protocol="tcp" accept'` `sudo firewall-cmd --reload` Disabling the service will prevent its functionality. A service restart or system reboot may be required for changes to take full effect.

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Get an email when Red Hat RHEL & SELinux publishes the next one.

See Red Hat RHEL & SELinux's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat RHEL & SELinux

More Red Hat Linux advisories

All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Download on the App StoreGet CVE alerts on AndroidSee app features

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.