<?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>DevSpace UI &lt;= 6.3.20 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/devspace-ui--6.3.20/</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>Tue, 02 Jan 2024 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/devspace-ui--6.3.20/feed.xml" rel="self" type="application/rss+xml"/><item><title>DevSpace UI Server WebSocket Origin Validation Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2024-01-devspace-websocket-vuln/</link><pubDate>Tue, 02 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-devspace-websocket-vuln/</guid><description>DevSpace's UI server WebSocket accepts connections from any origin, enabling attackers to access pod logs, interactive shells, and execute commands via cross-origin WebSocket connections; versions up to 6.3.20 are affected, patched in 6.3.21.</description><content:encoded><![CDATA[<p>DevSpace, a tool for developing and deploying applications in Kubernetes, contains a vulnerability in its UI server WebSocket implementation. Versions 6.3.20 and earlier do not properly validate the origin of WebSocket connections. This allows a malicious website, visited by a developer running the DevSpace UI, to establish a cross-origin WebSocket connection to <code>ws://127.0.0.1:8090</code>. Successful exploitation grants the attacker unauthorized access to sensitive functionalities, including real-time pod log streaming, opening interactive shells within running pods, and executing pre-defined pipeline commands. This poses a significant risk to developers using DevSpace as it allows unauthorized access to and control over their Kubernetes deployments. The vulnerability is identified as CVE-2026-42283.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>A developer runs the DevSpace UI, typically accessible at <code>ws://127.0.0.1:8090</code>.</li>
<li>The same developer uses a web browser to access the internet.</li>
<li>The developer visits a malicious website that contains JavaScript designed to exploit the DevSpace WebSocket vulnerability.</li>
<li>The malicious website&rsquo;s JavaScript establishes a WebSocket connection to the developer&rsquo;s local DevSpace UI server (<code>ws://127.0.0.1:8090</code>).</li>
<li>Because the DevSpace UI server lacks origin validation, it accepts the connection from the malicious website.</li>
<li>The attacker leverages the open WebSocket connection to access the <code>/api/logs</code> endpoint, streaming real-time pod logs.</li>
<li>The attacker utilizes the connection to execute commands via the <code>/api/command</code> endpoint.</li>
<li>The attacker gains a shell in the pod via the <code>/api/enter</code> endpoint, achieving code execution within the container.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows an attacker to gain unauthorized access to a developer&rsquo;s Kubernetes environment. This could lead to the exfiltration of sensitive information from pod logs, unauthorized execution of commands within pods, and potentially full compromise of the affected Kubernetes deployment. The impact is especially significant for developers working with sensitive data or critical infrastructure.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade DevSpace to version 6.3.21 or later to patch the vulnerability (CVE-2026-42283).</li>
<li>Implement network segmentation to limit access to the DevSpace UI server to trusted networks only.</li>
<li>Monitor network connections for unusual WebSocket connections to port 8090 using the provided Sigma rule.</li>
<li>Enable web server logging for unexpected requests to <code>/api/logs</code>, <code>/api/enter</code>, and <code>/api/command</code> endpoints originating from localhost, as detected by the provided Sigma rule.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>websocket</category><category>kubernetes</category><category>vulnerability</category></item></channel></rss>