<?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>Static Tundra — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/actors/static-tundra/</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 Jan 2024 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/actors/static-tundra/feed.xml" rel="self" type="application/rss+xml"/><item><title>Detection of Suspicious Cisco Configuration Changes via Archive Logging</title><link>https://feed.craftedsignal.io/briefs/2024-01-cisco-config-changes/</link><pubDate>Wed, 03 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-cisco-config-changes/</guid><description>This analytic detects suspicious configuration changes on Cisco devices by analyzing archive logs for activities such as backdoor account creation, SNMP community string modifications, and TFTP server configurations, potentially indicating attacker presence and lateral movement.</description><content:encoded><![CDATA[<p>This threat brief focuses on detecting malicious activity within Cisco IOS devices by analyzing configuration archive logs. Configuration archive logging captures all modifications made to a device&rsquo;s configuration, offering a detailed audit trail. Analyzing these logs allows for the identification of suspicious or malicious activities, such as the creation of backdoor accounts, modifications to SNMP community strings, and the setup of TFTP servers for potential data exfiltration. This detection method is crucial for identifying advanced attack campaigns, exemplified by threat actors like Static Tundra, who often manipulate network configurations to maintain persistence and facilitate lateral movement. The monitoring of configuration changes across different user sessions provides a comprehensive view of device activity.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker gains initial access to the network through an external vulnerability or compromised credentials.</li>
<li>Attacker leverages their initial access to authenticate to a Cisco IOS device.</li>
<li>The attacker modifies the device configuration to create a new user account with privilege level 15, effectively creating a backdoor.</li>
<li>The attacker changes the SNMP community string to gain unauthorized access to network monitoring data.</li>
<li>The attacker configures a TFTP server on the Cisco device to enable data exfiltration.</li>
<li>The attacker modifies the user table to elevate privileges of existing accounts.</li>
<li>The attacker uses the elevated privileges to move laterally within the network.</li>
<li>The attacker exfiltrates sensitive data using the configured TFTP server.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Compromised Cisco IOS devices can lead to significant network breaches, data exfiltration, and persistent access for malicious actors. Successful exploitation allows attackers to move laterally within the network, gain access to sensitive data, and maintain a foothold for future attacks. The CVE-2018-0171 vulnerability, related to Cisco Smart Install, can allow remote code execution, potentially impacting thousands of devices if not properly patched. Unauthorized configuration changes can disrupt network operations, compromise sensitive data, and damage an organization&rsquo;s reputation.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Enable Cisco IOS archive logging with the commands <code>archive</code> and <code>log config</code> in global configuration mode to generate the necessary logs for detection.</li>
<li>Configure command logging with <code>archive log config logging enable</code> and set appropriate logging levels with <code>logging trap informational</code> on Cisco devices to capture configuration changes.</li>
<li>Deploy the Sigma rule &ldquo;Cisco Privilege Escalation via Configuration Change&rdquo; to detect the creation of high-privilege accounts (All_Changes.command=&quot;<em>username</em>privilege 15*&quot;).</li>
<li>Deploy the Sigma rule &ldquo;Cisco SNMP Community String Modification&rdquo; to identify unauthorized changes to SNMP settings (All_Changes.command=&quot;<em>snmp-server community</em>&quot;).</li>
<li>Investigate any alerts generated by the Sigma rules, focusing on the source device (<code>dest</code>) and the user (<code>user</code>) involved, using the provided drilldown searches.</li>
<li>Monitor logs for CVE-2018-0171 and apply necessary patches.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">threat</category><category>cisco</category><category>network-security</category><category>configuration-change</category></item></channel></rss>