<?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>RConfig (&lt; 8.2.13) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/rconfig--8.2.13/</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>Mon, 24 Aug 2026 18:03:19 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/rconfig--8.2.13/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>Authentication Bypass and Privilege Escalation in rConfig</title><link>https://feed.craftedsignal.io/briefs/2026-08-rconfig-auth-bypass/</link><pubDate>Mon, 24 Aug 2026 18:03:19 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-rconfig-auth-bypass/</guid><description>rConfig versions 8.0.0 through 8.2.12 contain a logic flaw in route configuration that enables unauthenticated registration of administrator-privileged accounts, facilitating full system compromise.</description><content:encoded><![CDATA[<p>The vulnerability CVE-2026-77915 affects rConfig versions prior to 8.2.13. The issue stems from a redundant <code>Auth::routes()</code> call within the <code>routes/web.php</code> file, which inadvertently re-enables the registration endpoint after it had been explicitly disabled by the developers. When an unauthenticated attacker accesses the <code>/register</code> endpoint and creates a new account, the application fails to assign a restricted role during the account creation process. Consequently, the <code>users.role</code> column in the underlying database defaults to the 'Admin' privilege level. This flaw allows an attacker to achieve full administrative access without prior authentication, providing them with the ability to manage device configurations, harvest sensitive credentials stored within the application, access user data, and generate new API tokens for further persistence. This vulnerability is critical due to the ease of exploitation and the resulting high-privileged access granted to unauthorized users.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated attackers to obtain full administrative control over the rConfig instance. This access exposes the entirety of the network device management environment, including administrative credentials for managed network infrastructure, sensitive user information, and application API keys. Compromise of an rConfig instance could lead to widespread unauthorized access or configuration changes across the target organization's network devices.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately update rConfig instances to version 8.2.13 or later to patch the registration route conflict.</li>
<li>Audit existing user accounts for any entries created or modified after the date the application was deployed, specifically looking for users with 'Admin' roles created through the registration controller.</li>
<li>Review all API tokens for unexpected or suspicious issuance and revoke any tokens associated with unauthorized administrative accounts.</li>
<li>Deploy the provided webserver detection rule to monitor for unauthorized access attempts to the <code>/register</code> endpoint.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>vulnerability</category><category>web-application</category><category>authentication-bypass</category><category>privilege-escalation</category></item></channel></rss>