<?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>Openvpn — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/openvpn/</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 14:29:22 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/openvpn/feed.xml" rel="self" type="application/rss+xml"/><item><title>OpenVPN-auth-oauth2 Authentication Bypass in Plugin Mode</title><link>https://feed.craftedsignal.io/briefs/2026-04-openvpn-auth-bypass/</link><pubDate>Wed, 22 Apr 2026 14:29:22 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-openvpn-auth-bypass/</guid><description>A critical authentication bypass vulnerability exists in openvpn-auth-oauth2 versions 1.26.3 through 1.27.2 when deployed in the experimental plugin mode; clients that do not support WebAuth/SSO are incorrectly granted VPN access without completing OIDC authentication.</description><content:encoded><![CDATA[<p>OpenVPN-auth-oauth2, a plugin for OpenVPN, is susceptible to an authentication bypass vulnerability in versions 1.26.3 through 1.27.2 when deployed in the experimental plugin mode. This flaw allows unauthenticated VPN access for clients that do not support WebAuth/SSO. Specifically, standard OpenVPN clients like the Linux CLI <code>openvpn</code>, which do not advertise WebAuth/SSO support (<code>IV_SSO=webauth</code>), can bypass OIDC authentication and gain full network access. The default management-interface mode is not affected. Successful exploitation grants unauthorized access to the internal network behind the VPN. This vulnerability is addressed in version 1.27.3.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies an OpenVPN server running openvpn-auth-oauth2 in experimental plugin mode (versions 1.26.3 - 1.27.2).</li>
<li>Attacker uses a standard OpenVPN client (e.g., Linux <code>openvpn</code> CLI) that does not support WebAuth/SSO.</li>
<li>The client initiates a connection to the OpenVPN server, bypassing the expected WebAuth/SSO flow.</li>
<li>The openvpn-auth-oauth2 plugin attempts to deny the client by writing &ldquo;0&rdquo; to the <code>auth_control_file</code>.</li>
<li>The plugin incorrectly returns <code>OPENVPN_PLUGIN_FUNC_SUCCESS</code> to the OpenVPN server.</li>
<li>OpenVPN interprets the <code>FUNC_SUCCESS</code> return code as successful authentication, ignoring the &ldquo;0&rdquo; in the <code>auth_control_file</code>.</li>
<li>The OpenVPN server grants the unauthenticated client full access to the internal network behind the VPN.</li>
<li>Attacker gains unauthorized access to internal resources and performs malicious activities such as data exfiltration or lateral movement.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability grants unauthenticated attackers full access to the internal network behind the OpenVPN server. This could lead to data breaches, lateral movement within the network, and potential compromise of sensitive systems. The vulnerability affects any deployment using the experimental plugin mode with vulnerable versions. This could result in significant financial losses, reputational damage, and legal repercussions for affected organizations.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately upgrade to openvpn-auth-oauth2 version 1.27.3 to apply the fix described in commit <a href="https://github.com/jkroepke/openvpn-auth-oauth2/commit/36f69a6c67c1054da7cbfa04ced3f0555127c8f2"><code>36f69a6</code></a>.</li>
<li>If immediate upgrade is not feasible, switch to the standalone management client mode (the default, non-plugin deployment) as a workaround.</li>
<li>Monitor OpenVPN server logs for connection attempts from clients that do not support WebAuth/SSO (identified by missing <code>IV_SSO=webauth</code> in the logs) and correlate with network access activity.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>openvpn</category><category>authentication-bypass</category><category>vpn</category></item><item><title>WAGO PLC OpenVPN Configuration Vulnerability (CVE-2024-1490)</title><link>https://feed.craftedsignal.io/briefs/2026-04-wago-plc-openvpn-rce/</link><pubDate>Thu, 09 Apr 2026 11:16:19 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-wago-plc-openvpn-rce/</guid><description>An authenticated remote attacker with high privileges can exploit the OpenVPN configuration via the web-based management interface of a WAGO PLC to achieve arbitrary command execution on the device.</description><content:encoded><![CDATA[<p>CVE-2024-1490 describes a critical vulnerability affecting WAGO Programmable Logic Controllers (PLCs). A remote attacker with existing high-privilege access to the PLC&rsquo;s web-based management interface can exploit the OpenVPN configuration. The vulnerability stems from insufficient input validation within the OpenVPN configuration settings. If the PLC&rsquo;s OpenVPN setup permits user-defined scripts, a malicious actor can inject arbitrary shell commands. Successful exploitation allows the attacker to execute arbitrary code on the underlying operating system of the WAGO PLC, potentially leading to full device compromise. This vulnerability was reported by CERT VDE and impacts WAGO PLCs that utilize a vulnerable web-based management interface and permit user-defined scripts in their OpenVPN configuration.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker gains initial high-privilege access to the WAGO PLC&rsquo;s web-based management interface.</li>
<li>The attacker navigates to the OpenVPN configuration section within the management interface.</li>
<li>The attacker identifies that the OpenVPN configuration allows for user-defined scripts.</li>
<li>The attacker crafts a malicious OpenVPN configuration file or injects malicious commands via existing configuration options. This configuration contains embedded shell commands designed for execution on the PLC.</li>
<li>The attacker uploads or applies the modified OpenVPN configuration to the WAGO PLC through the web interface.</li>
<li>The WAGO PLC processes the OpenVPN configuration, leading to the execution of the attacker-supplied shell commands.</li>
<li>The attacker achieves arbitrary code execution on the underlying operating system of the WAGO PLC.</li>
<li>The attacker can then use this initial foothold to perform further actions, such as deploying malware, exfiltrating sensitive information, or disrupting industrial processes.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2024-1490 allows an attacker to execute arbitrary code on a WAGO PLC. This can lead to complete compromise of the device, potentially affecting the industrial processes it controls. An attacker could disrupt operations, manipulate data, or use the compromised PLC as a pivot point for further attacks within the industrial network. The severity of the impact depends on the role of the compromised PLC within the industrial environment, potentially leading to significant financial losses, safety incidents, or reputational damage.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Restrict access to the WAGO PLC&rsquo;s web-based management interface by enforcing strong authentication and authorization mechanisms to prevent unauthorized access (refer to CVE-2024-1490).</li>
<li>Disable or restrict the use of user-defined scripts within the OpenVPN configuration to mitigate the risk of command injection (refer to CVE-2024-1490).</li>
<li>Monitor web server logs for suspicious activity related to OpenVPN configuration changes, looking for unusual POST requests or configuration parameters (see &ldquo;rules&rdquo; section below).</li>
<li>Implement regular security audits of WAGO PLC configurations, focusing on OpenVPN settings and user-defined scripts (refer to CVE-2024-1490).</li>
<li>Review and apply the security recommendations provided by CERT VDE in their advisory, available at <a href="https://certvde.com/de/advisories/VDE-2024-008">https://certvde.com/de/advisories/VDE-2024-008</a>.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cve-2024-1490</category><category>wago-plc</category><category>openvpn</category><category>rce</category><category>code-injection</category></item></channel></rss>