<?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/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cpe:2.3:a:sogo:sogo:*:*:*:*:*:*:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3asogosogo/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 12 Nov 2026 16:50:53 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3asogosogo/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>SOGo: TOTP authentication bypass (CVE-2026-127131)</title><link>https://feed.craftedsignal.io/briefs/2026-11-sogo-totp-bypass-cve-2026-127131/</link><pubDate>Thu, 12 Nov 2026 16:50:53 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-sogo-totp-bypass-cve-2026-127131/</guid><description>SOGo versions prior to 5.12.13 contain a vulnerability in TOTP verification that allows brute-force of second-factor codes, enabling attackers with valid passwords to bypass multi-factor authentication.</description><content:encoded><![CDATA[<p>SOGo versions before 5.12.13 are vulnerable to an authentication bypass due to missing rate limiting on TOTP verification. Attackers who possess a valid user password can conduct indefinite brute-force attacks against the TOTP second-factor because failed verification attempts do not increment the login failure counter, and the SOGoMaximumFailedLoginCount configuration setting does not apply to these attempts.</p>
<h2 id="impact">Impact</h2>
<p>Attackers can bypass multi-factor authentication by programmatically guessing TOTP codes. This exposes accounts to unauthorized access if a primary password has already been compromised.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade SOGo to version 5.12.13 or later immediately to apply the rate limiting fix.</li>
<li>Review authentication logs for patterns of high-frequency failed TOTP attempts originating from single user accounts or IP addresses.</li>
<li>Audit existing user passwords for compromise, as the threat relies on prior acquisition of the password.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>SOGo: Improper authentication restriction in password recovery (CVE-2026-127111)</title><link>https://feed.craftedsignal.io/briefs/2026-11-sogo-auth-bypass-cve-2026-127111/</link><pubDate>Thu, 12 Nov 2026 16:50:45 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-sogo-auth-bypass-cve-2026-127111/</guid><description>SOGo versions prior to 5.12.13 are vulnerable to improper restriction of authentication attempts, enabling unauthenticated attackers to perform brute-force attacks against security questions and achieve full account takeover.</description><content:encoded><![CDATA[<p>SOGo versions prior to 5.12.13 contain an improper restriction of excessive authentication attempts in the password recovery process. An unauthenticated attacker can repeatedly guess secret-question answers via the passwordRecoveryCheck endpoint without rate limiting or lockout protections. Successful brute-forcing allows the attacker to obtain a recovery JWT, which can then be used to reset an account password without requiring the old credential. This results in full account takeover for accounts not protected by time-based one-time passwords (TOTP).</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies a target account with a configured secret question.</li>
<li>Attacker interacts with the passwordRecoveryCheck API endpoint.</li>
<li>Attacker submits repeated, automated requests containing guessed answers to the secret question.</li>
<li>Attacker successfully guesses the correct answer due to a lack of rate limiting.</li>
<li>Application issues a recovery JWT to the attacker.</li>
<li>Attacker uses the recovery JWT to reset the victim's account password via the password reset functionality.</li>
<li>Attacker logs into the target account via the connect endpoint, achieving full account takeover.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation results in full account takeover for any account that has not enabled TOTP. This allows unauthorized access to sensitive user data and account functions.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Upgrade SOGo to version 5.12.13 or later immediately. For environments where patching cannot occur immediately, monitor web server logs for anomalous volumes of POST requests targeting the passwordRecoveryCheck endpoint from single source IPs.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>