Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

Time-based Blind SQL Injection in Cloudlog v2.6.15 (qsoresults parameter)

IdentifiersCVE-2024-44065CWE-89· Improper Neutralization of Special…

CVE-2024-44065 is a critical time-based blind SQL injection vulnerability in Cloudlog v2.6.15. The vulnerability exists at the /index.php/logbookadvanced/search endpoint, specifically in the qsoresults parameter. Unsanitized user input in this parameter is directly incorporated into SQL queries, allowing attackers to inject arbitrary SQL code. This can be exploited remotely without authentication or user interaction, enabling attackers to execute time-based blind SQL injection attacks and extract sensitive data from the backend database.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary SQL commands against the Cloudlog database. This can result in unauthorized access to sensitive data, modification or deletion of database contents, and potentially full compromise of the application's confidentiality, integrity, and availability. The CVSS 3.1 base score is 9.8, indicating critical risk.

Mitigation

If you can’t patch tonight, do this now.

As an immediate mitigation, implement strict input validation and sanitization on the qsoresults parameter and any other user-supplied data. Deploy web application firewalls (WAFs) with rules to detect and block SQL injection attempts. Restrict database user privileges to minimize the impact of a successful injection. Monitor logs for suspicious activity targeting the vulnerable endpoint.

Remediation

Patch, then assume compromise.

Update Cloudlog to a patched version that addresses this vulnerability. Ensure all user input is properly sanitized and validated. Refactor the affected code to use parameterized queries or prepared statements to prevent SQL injection. Review and update any custom code that interacts with the database to follow secure coding practices.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
MagicbugCloudlogapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.