<?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>Bruteforce — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/bruteforce/</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, 22 Apr 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/bruteforce/feed.xml" rel="self" type="application/rss+xml"/><item><title>Fortra GoAnywhere MFT SSH Key Brute-Force Vulnerability (CVE-2025-14362)</title><link>https://feed.craftedsignal.io/briefs/2026-04-goanywhere-bruteforce/</link><pubDate>Wed, 22 Apr 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-goanywhere-bruteforce/</guid><description>Fortra's GoAnywhere MFT prior to 7.10.0 is vulnerable to brute-force attacks on SSH keys because the login limit is not enforced on the SFTP service when Web Users are configured to log in with an SSH Key.</description><content:encoded><![CDATA[<p>CVE-2025-14362 is a vulnerability affecting Fortra&rsquo;s GoAnywhere MFT servers prior to version 7.10.0. The vulnerability arises because the login limit is not enforced on the SFTP service when a Web User is configured to authenticate using an SSH key. This lack of enforcement allows attackers to conduct brute-force attacks against the SSH key, attempting to guess the key through repeated authentication attempts. Successful exploitation grants unauthorized access to the GoAnywhere MFT server, potentially leading to data breaches, system compromise, and other malicious activities. Defenders should prioritize patching vulnerable GoAnywhere MFT instances to version 7.10.0 or later.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies a GoAnywhere MFT server running a version prior to 7.10.0.</li>
<li>Attacker determines that the GoAnywhere MFT server allows Web Users to authenticate using SSH keys.</li>
<li>Attacker attempts to authenticate to the SFTP service using a series of generated SSH keys.</li>
<li>Due to the lack of login limit enforcement, the attacker can make unlimited authentication attempts without being locked out.</li>
<li>The attacker continues brute-forcing SSH keys until a valid key is guessed, or an exploitable weakness is found.</li>
<li>Upon successful authentication, the attacker gains unauthorized access to the GoAnywhere MFT server.</li>
<li>The attacker can then upload/download arbitrary files, execute commands, and potentially move laterally within the network.</li>
<li>The final objective is to exfiltrate sensitive data or establish a persistent foothold within the target environment.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2025-14362 can lead to unauthorized access to sensitive data managed by the GoAnywhere MFT server. This could include financial records, customer data, intellectual property, and other confidential information. The number of victims is dependent on the exposure of vulnerable GoAnywhere MFT servers. Sectors commonly using MFT solutions, such as finance, healthcare, and government, are at increased risk. The impact of a successful attack can range from data breaches and financial loss to reputational damage and legal liabilities.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Fortra GoAnywhere MFT to version 7.10.0 or later to patch CVE-2025-14362 (reference: Overview).</li>
<li>Implement rate limiting on SSH authentication attempts at the network or host level to mitigate brute-force attacks, even after patching (reference: Attack Chain).</li>
<li>Monitor SFTP logs for excessive failed authentication attempts originating from the same source IP address using a Sigma rule similar to the one provided below (reference: Rules).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>goanywhere</category><category>mft</category><category>bruteforce</category><category>ssh</category></item><item><title>Windows Remote Desktop Network Bruteforce Attempt</title><link>https://feed.craftedsignal.io/briefs/2024-01-rdp-bruteforce/</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-rdp-bruteforce/</guid><description>This detection identifies potential RDP brute force attacks by monitoring network traffic for RDP application activity by detecting source IPs that have made more than 10 connection attempts to the same RDP port on a host within a one-hour window.</description><content:encoded><![CDATA[<p>This analytic identifies potential Remote Desktop Protocol (RDP) brute force attacks by monitoring network traffic for RDP application activity. It detects potential RDP brute force attacks by identifying source IPs that have made more than 10 connection attempts to the same RDP port on a host within a one-hour window. The results are presented in a table that includes the source and destination IPs, destination port, number of attempts, and the times of the first and last connection attempts, helping to prioritize IPs based on the intensity of activity. This activity can lead to account compromise and potential ransomware deployment.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker scans the network to identify systems with open RDP ports (TCP 3389).</li>
<li>The attacker initiates multiple RDP connection attempts to a target host, using a list of common usernames and passwords or compromised credentials.</li>
<li>The firewall logs each connection attempt, recording the source and destination IPs, ports, and timestamps.</li>
<li>Sysmon logs the network connections with Event ID 3.</li>
<li>The attacker continues to attempt connections, typically exceeding 10 attempts within an hour.</li>
<li>Upon successful authentication, the attacker gains unauthorized access to the target system.</li>
<li>The attacker may then install malware, move laterally, or exfiltrate sensitive data.</li>
<li>The attacker might deploy ransomware like SamSam or Ryuk, as referenced in external reports.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful RDP brute force attacks can lead to unauthorized access to systems, data breaches, malware infections, and ransomware deployment. Compromised systems can be used as a staging point for further attacks within the network. The references indicate that ransomware attacks have been delivered using RDP brute-force techniques.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Ensure network traffic data is populating the Network_Traffic data model to enable the provided search query.</li>
<li>Deploy the Sigma rule <code>RDP Bruteforce via Network Traffic</code> to detect brute force attempts based on network connection patterns.</li>
<li>Adjust the count and duration thresholds in the detection query to tune the sensitivity for your environment.</li>
<li>Investigate source IPs identified by the detection rule as potential attackers.</li>
<li>Monitor Sysmon EventID 3 for network connections to detect RDP brute-force attempts.</li>
<li>Review the referenced Zscaler and ReliaQuest articles for additional context and mitigation strategies.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>rdp</category><category>bruteforce</category><category>credential-access</category><category>windows</category><category>network</category></item></channel></rss>