<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Mssql — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/mssql/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 03 Jul 2024 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/mssql/feed.xml" rel="self" type="application/rss+xml"/><item><title>Potential Veeam Credential Access via SQL Commands</title><link>https://feed.craftedsignal.io/briefs/2024-07-veeam-credential-access/</link><pubDate>Wed, 03 Jul 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-07-veeam-credential-access/</guid><description>Attackers can leverage sqlcmd.exe or PowerShell commands like Invoke-Sqlcmd to access Veeam credentials stored in MSSQL databases, potentially targeting backups for destructive operations such as ransomware attacks.</description><content:encoded><![CDATA[<p>Attackers are increasingly targeting backup infrastructure to maximize the impact of ransomware and data exfiltration attacks. Veeam, a popular backup and disaster recovery solution, stores credentials for backup operations in MSSQL databases. An attacker who gains access to these databases may attempt to use tools like <code>sqlcmd.exe</code> or PowerShell commands (e.g., <code>Invoke-Sqlcmd</code>) to extract and decrypt these credentials. This tactic allows the attacker to compromise the backups themselves, preventing recovery and increasing pressure on the victim. This activity has been observed in real-world incidents, such as those involving the Diavol ransomware. Defenders should monitor for suspicious command-line activity targeting Veeam credentials within MSSQL environments.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Initial access to the target environment is gained through methods such as phishing or exploiting a vulnerability in a public-facing application.</li>
<li>The attacker performs reconnaissance to identify the location of the Veeam MSSQL database server.</li>
<li>The attacker obtains valid credentials or exploits a vulnerability to gain access to the Veeam MSSQL database server.</li>
<li>The attacker executes <code>sqlcmd.exe</code> or uses PowerShell commands (e.g., <code>Invoke-Sqlcmd</code>) to query the <code>[VeeamBackup].[dbo].[Credentials]</code> table.</li>
<li>The attacker retrieves the encrypted Veeam credentials from the database.</li>
<li>The attacker decrypts the Veeam credentials using custom scripts or tools, potentially leveraging the Veeam backup server itself.</li>
<li>The attacker uses the compromised Veeam credentials to access and delete or encrypt backup data.</li>
<li>The attacker deploys ransomware on the remaining systems, knowing that recovery from backups is now impossible.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful compromise of Veeam credentials can have devastating consequences. Attackers can encrypt or delete backup data, making recovery impossible and significantly increasing the impact of ransomware attacks. This can lead to prolonged downtime, data loss, financial losses, and reputational damage. Organizations relying on Veeam for backup and recovery should prioritize monitoring and securing their Veeam infrastructure to prevent credential access and backup compromise.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Enable Sysmon process creation logging to capture command-line activity, specifically <code>sqlcmd.exe</code> and PowerShell.</li>
<li>Deploy the Sigma rule &ldquo;Potential Veeam Credential Access Command&rdquo; to detect suspicious command executions targeting Veeam credentials in MSSQL databases.</li>
<li>Review and restrict access controls to the Veeam MSSQL database, ensuring only authorized personnel and services have access.</li>
<li>Monitor for unusual login activity and failed login attempts to the Veeam MSSQL database server.</li>
<li>Implement multi-factor authentication for all accounts with access to Veeam infrastructure.</li>
<li>Regularly audit Veeam backup configurations and logs to identify any unauthorized modifications or access attempts.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>veeam</category><category>credential-access</category><category>mssql</category><category>windows</category><category>ransomware</category></item></channel></rss>