<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security advisories on OpenWrt</title><link>https://openwrt.org/advisories/</link><description>Recent content in Security advisories on OpenWrt</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 16 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://openwrt.org/advisories/index.xml" rel="self" type="application/rss+xml"/><item><title>Dropbear privilege escalation via Unix domain socket forwarding</title><link>https://openwrt.org/advisories/2025-12-16-1/</link><pubDate>Tue, 16 Dec 2025 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2025-12-16-1/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>A privilege escalation vulnerability has been discovered in the Dropbear SSH server affecting configurations where multiple local users are allowed to authenticate via SSH.&lt;/p>
&lt;p>When processing TCP or Unix domain socket forwardings requested by an authenticated SSH client, Dropbear executes the forwarding operations &lt;strong>as root&lt;/strong>, only switching to the logged-in user’s UID/GID after establishing the session shell. With the recently added support for &lt;strong>Unix domain socket forwarding&lt;/strong>, this behavior allows any authenticated non-root SSH user to connect to arbitrary local root-owned Unix sockets as if they were the root user.&lt;/p></description></item><item><title>ltq-ptm: local privilege escalation</title><link>https://openwrt.org/advisories/2025-10-22-2/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2025-10-22-2/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>Local users could read and write arbitrary kernel memory using the ioctls of the ltq-ptm driver which is used to drive the datapath of the DSL line.&lt;/p>
&lt;h2 id="requirements">REQUIREMENTS&lt;/h2>
&lt;p>This only effects the lantiq target supporting xrx200, danube and amazon SoCs from Lantiq/Intel/MaxLinear with the DSL in PTM mode. The DSL driver for the VRX518 is not affected. ATM mode is also not affected. Most VDSL lines use PTM mode and most ADSL lines use ATM mode.&lt;/p></description></item><item><title>ubusd: heap buffer overflow</title><link>https://openwrt.org/advisories/2025-10-22-1/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2025-10-22-1/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>ubusd contains a heap buffer overflow in the event registration parsing code. This allows an attacker to modify the head and potentially execute arbitrary code in the context of the ubus daemon.&lt;/p>
&lt;p>The affected code is executed before running the ACL checks, all ubus clients are able to send such messages.&lt;/p>
&lt;p>In addition to the heap corruption, the crafted subscription also results in a bypass of the listen ACL.&lt;/p></description></item><item><title>OpenWrt Attended SysUpgrade server: Build artifact poisoning via truncated SHA-256 hash and command injection</title><link>https://openwrt.org/advisories/2024-12-06/</link><pubDate>Fri, 06 Dec 2024 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2024-12-06/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>Due to the combination of the command injection in the &lt;a href="../docs/guide-user/additional-software/imagebuilder">imagebuilder&lt;/a> image and the truncated SHA-256 hash included in the build request hash, an attacker can pollute the legitimate image by providing a package list that causes the hash collision. The issue consists of two main components:&lt;/p>
&lt;p>1. &lt;strong>Command Injection in Imagebuilder&lt;/strong>: During image builds, user-supplied package names are incorporated into &lt;code>make&lt;/code> commands without proper sanitization. This allows malicious users to inject arbitrary commands into the build process, resulting in the production of malicious firmware images signed with the legitimate build key.&lt;/p></description></item><item><title>Multiple issues in mac80211 and cfg80211</title><link>https://openwrt.org/advisories/2022-10-17-1/</link><pubDate>Mon, 17 Oct 2022 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2022-10-17-1/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>Multiple vulnerabilities were found in the Linux Kernel mac80211 and cfg80211 framework.
OpenWrt takes the mac80211 and cfg80211 framework from the wireless backports project which copies it from a more recent Linux kernel version.&lt;/p>
&lt;p>These vulnerabilities are in the multi BSSID (MBSSID) beacon parsing code and the P2P-device beacon parsing code.&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41674">CVE-2022-41674&lt;/a>: fix u8 overflow in cfg80211_update_notlisted_nontrans (max 256 byte overwrite) (RCE)&lt;/li>
&lt;li>&lt;a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42719">CVE-2022-42719&lt;/a>: wifi: mac80211: fix MBSSID parsing use-after-free use after free condition (RCE)&lt;/li>
&lt;li>&lt;a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42720">CVE-2022-42720&lt;/a>: wifi: cfg80211: fix BSS refcounting bugs ref counting use-after-free possibilities (RCE)&lt;/li>
&lt;li>&lt;a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42721">CVE-2022-42721&lt;/a>: wifi: cfg80211: avoid nontransmitted BSS list corruption list corruption (DOS)&lt;/li>
&lt;li>&lt;a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42722">CVE-2022-42722&lt;/a>: wifi: mac80211: fix crash in beacon protection for P2P-device NULL ptr dereference crash (DOS)&lt;/li>
&lt;/ul>
&lt;h2 id="requirements">REQUIREMENTS&lt;/h2>
&lt;p>The vulnerabilities are mostly in the Wifi beacon parsing code. OpenWrt operating as Wifi AP or Wifi client is affected when it scans for Wifi networks.
A malicious attacker could exploit this by sending specially crafted packets while the target is scanning for Wifi networks.
A malicious attacker has to be physically close to the target to exploit these vulnerabilities.
This can be exploited by attackers which are not necessary part of the network, no authentication needed. Wifi drivers in OpenWrt will parse beacons from arbitrary Wifi devices nearby.&lt;/p></description></item><item><title>wolfSSL buffer overflow during a TLS 1.3 handshake</title><link>https://openwrt.org/advisories/2022-10-04-1/</link><pubDate>Tue, 04 Oct 2022 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2022-10-04-1/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>In wolfSSL before 5.5.1, malicious clients can cause a buffer overflow on server during a TLS 1.3 handshake.&lt;/p>
&lt;p>This occurs when an attacker supposedly resumes a previous TLS session. During the resumption Client Hello a Hello Retry Request must be triggered. Both Client Hellos are required to contain a list of duplicate cipher suites to trigger the buffer overflow. In total, two Client Hellos have to be sent: one in the resumed session, and a second one as a response to a Hello Retry Request message.&lt;/p></description></item><item><title>luci-app-ddns: Multiple authenticated RCEs</title><link>https://openwrt.org/advisories/2021-08-01-3/</link><pubDate>Sun, 01 Aug 2021 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2021-08-01-3/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>An authenticated user in LuCI is able to inject shell code in luci-app-ddns.
Multiple variables in the luci-app-ddns applications where not validated before they were executed on the system’s shell, which could be exploited by adding system shell commands.&lt;/p>
&lt;h2 id="requirements">REQUIREMENTS&lt;/h2>
&lt;p>To exploit this vulnerability the attackers needs access to LuCI and the extra application luci-app-ddns has to be installed.
The attacker is then able to inject code which is executed on the shell of the system.&lt;/p></description></item><item><title>Stored XSS in hostname UCI variable</title><link>https://openwrt.org/advisories/2021-08-01-2/</link><pubDate>Sun, 01 Aug 2021 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2021-08-01-2/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>Multiple OpenWrt LuCI templates, including the one shipped by default, integrated the content of the UCI hostname variable without stripping it from malicious JavaScript.
This allowed an attacker, which can control the content of the UCI hostname variable, to inject a arbitrary JavaScript into LuCI.&lt;/p>
&lt;p>The following LuCI packages were affected:&lt;/p>
&lt;ul>
&lt;li>luci-theme-bootstrap&lt;/li>
&lt;li>luci-theme-material&lt;/li>
&lt;li>luci-theme-openwrt&lt;/li>
&lt;/ul>
&lt;h2 id="requirements">REQUIREMENTS&lt;/h2>
&lt;p>The attacker needs permission to change the UCI hostname variable. Normally only the root user is allowed to do this.
In a normal OpenWrt installation such a user would already be allowed to do arbitrary changes to LuCI including changing the LuCI templates.&lt;/p></description></item><item><title>XSS via missing input validation of host names displayed</title><link>https://openwrt.org/advisories/2021-08-01-1/</link><pubDate>Sun, 01 Aug 2021 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2021-08-01-1/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>Missing input validation of host names displayed in OpenWrt LuCI web-interface leads to Cross-site scripting, which can be used to gain full control over the affected system.&lt;/p>
&lt;h2 id="requirements">REQUIREMENTS&lt;/h2>
&lt;p>Users need to visit the LuCI “Connection status” page of the router and activate the host name resolution. The attackers need to hold a connection to the OpenWrt router which is displayed in the Web-interface, ie. via sending ICMP &lt;em>ping&lt;/em> messages.&lt;/p></description></item><item><title>netifd and odhcp6c routing loop on IPv6 point to point links</title><link>https://openwrt.org/advisories/2021-02-02-1/</link><pubDate>Tue, 02 Feb 2021 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2021-02-02-1/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>In case a link prefix route points to a point-to-point link it can trigger a routing loop if the destination IPv6 address belongs to the prefix and is not a local IPv6 address. If such a packet is received and not directed to a local IPv6 address it will be routed back to the point-to-point link due to the link prefix route; the upstream ISP router will in its turn route the IPv6 packet back due to the assigned prefix route creating a “ping pong” effect.&lt;/p></description></item><item><title>wolfSSL heap buffer overflow in RsaPad_PSS</title><link>https://openwrt.org/advisories/2021-02-02-2/</link><pubDate>Tue, 02 Feb 2021 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2021-02-02-2/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>RsaPad_PSS in wolfcrypt/src/rsa.c in wolfSSL before 4.6.0 has an out-of-bounds write for certain relationships between key size and digest size. The issue is marked as critical with CVSS score of 9.8.&lt;/p>
&lt;h2 id="requirements">REQUIREMENTS&lt;/h2>
&lt;p>FIXME&lt;/p>
&lt;p>&lt;em>It’s still work in progress, there is not that much information about it
available yet, but according to the very high CVSS score of &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2020-36177">9.8&lt;/a> (10 is most
severe) it’s likely, that this issue has RCE potential.&lt;/em>&lt;/p></description></item><item><title>dnsmasq multiple vulnerabilities</title><link>https://openwrt.org/advisories/2021-01-19-1/</link><pubDate>Tue, 19 Jan 2021 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2021-01-19-1/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>Dnsmasq has two sets of vulnerabilities, one set of memory corruption issues
handling DNSSEC and a second set of issues validating DNS responses. These
vulnerabilities could allow an attacker to corrupt memory on the target device
and perform cache poisoning attacks against the target environment.&lt;/p>
&lt;p>These vulnerabilities are also tracked as ICS-VU-668462 and referred to as
&lt;a href="https://www.jsof-tech.com/disclosures/dnspooq/">DNSpooq&lt;/a>.&lt;/p>
&lt;p>&lt;a href="https://www.jsof-tech.com">JSOF&lt;/a> reported multiple buffer overflow
vulnerabilities in dnsmasq due to boundary checking errors in DNSSEC handling
code.&lt;/p></description></item><item><title>OpenWrt forum break-in on 16-Jan-2021</title><link>https://openwrt.org/advisories/2021-01-17-1/</link><pubDate>Sun, 17 Jan 2021 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2021-01-17-1/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>Around 0400 GMT on 16 Jan 2021, an administrator account on the OpenWrt forum (&lt;a href="https://forum.openwrt.org">https://forum.openwrt.org&lt;/a>) was breached. It is not known how the account was accessed: the account had a good password, but did not have two-factor authentication enabled.&lt;/p>
&lt;p>The intruder was able to download a copy of the user list that contains email addresses, handles, and other statistical information about the users of the forum. Although we do not believe the intruder could download the database, from an abundance of caution, we are following the advice of the Discourse community and have reset all passwords on the Forum, and flushed any API keys.&lt;/p></description></item><item><title>libuci import heap use after free</title><link>https://openwrt.org/advisories/2020-12-09-2/</link><pubDate>Wed, 09 Dec 2020 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2020-12-09-2/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>Possibly exploitable vulnerability was found in Unified Config Interface (UCI)
library named libuci, specifically in uci_import() C API function.&lt;/p>
&lt;p>&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2020-28951">CVE-2020-28951&lt;/a> has been assigned to this issue.&lt;/p>
&lt;h2 id="requirements">REQUIREMENTS&lt;/h2>
&lt;p>In order to exploit this vulnerability a malicious attacker would need to
provide specially crafted config file to uci_import() C API function. For
example, this is possible with UCI CLI by following shell command:&lt;/p>
&lt;pre>&lt;code> uci import -f malicious.config
&lt;/code>&lt;/pre>
&lt;h2 id="mitigations">MITIGATIONS&lt;/h2>
&lt;p>To fix this issue, update the affected libuci package using the command below.&lt;/p></description></item><item><title>Linux kernel - ICMP rate limiting can be used to facilitate DNS poisoning attack</title><link>https://openwrt.org/advisories/2020-12-09-1/</link><pubDate>Wed, 09 Dec 2020 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2020-12-09-1/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>A flaw has been found in the ICMP rate limiting algorithm of the Linux kernel.&lt;/p>
&lt;p>This flaw allows an off-path attacker to quickly determine open ephemeral ports
that are used by applications making outbound connections.&lt;/p>
&lt;p>This can be exploited by an off-path attacker to more easily perform a DNS
cache poisoning attack. Such an attack normally involves trying all possible
values of the UDP source port and the DNS transaction ID, which is considered
difficult to do.
With this flaw, the attacker can quickly guess the UDP source port, and then it
only has to try all possible values of the DNS transaction ID, which is easier to do:
the transaction ID only has 16 bits.
It should be noted that the attacker also needs to know the actual query sent by
the resolver.&lt;/p></description></item><item><title>relayd out-of-bounds reads of heap data and possible buffer overflow</title><link>https://openwrt.org/advisories/2020-05-06-2/</link><pubDate>Wed, 06 May 2020 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2020-05-06-2/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>&lt;code>relayd&lt;/code> in OpenWrt through 19.07.2 and 18.06.8 has potential for out-of-bounds reads of heap data and possible buffer overflow.&lt;/p>
&lt;p>&lt;code>relayd&lt;/code> is a transparent routing / relay daemon for OpenWrt. It can be used to &lt;a href="../docs/guide-user/network/wifi/relay_configuration">relay traffic between two networks&lt;/a>, including DHCP and broadcast, when other options don’t work or are too complex to implement.&lt;/p>
&lt;p>We have not been made aware of any exploits at this time, however users are advised to update the &lt;code>relayd&lt;/code> package to &lt;strong>2020-04-25-f4d759be-1&lt;/strong> or later.&lt;/p></description></item><item><title>umdns out-of-bounds reads of heap data and possible buffer overflow</title><link>https://openwrt.org/advisories/2020-05-06-1/</link><pubDate>Wed, 06 May 2020 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2020-05-06-1/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>&lt;code>umdns&lt;/code> in OpenWrt through 18.06.8 and 19.07.2 has potential for out-of-bounds reads of heap data and possible buffer overflow.&lt;/p>
&lt;p>&lt;code>umdns&lt;/code> is the OpenWrt Multicast DNS Daemon.&lt;/p>
&lt;p>We have not been made aware of any exploits at this time, however users are advised to update the &lt;code>umdns&lt;/code> package to &lt;strong>2020-04-25-cdac0460-1&lt;/strong> or later.&lt;/p>
&lt;p>&lt;a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11750">CVE-2020-11750&lt;/a> has been assigned to this issue.&lt;/p>
&lt;h2 id="requirements">REQUIREMENTS&lt;/h2>
&lt;p>The &lt;code>umdns&lt;/code> package is not part of the default package set: &lt;a href="../downloads/">official OpenWrt images provided for download&lt;/a> do not contain &lt;code>umdns&lt;/code>. However, third-party firmware images based on OpenWrt may contain &lt;code>umdns&lt;/code> by default.&lt;/p></description></item><item><title>ppp buffer overflow vulnerability</title><link>https://openwrt.org/advisories/2020-02-21-1/</link><pubDate>Fri, 21 Feb 2020 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2020-02-21-1/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>A remotely exploitable vulnerability was found in Point-to-Point Protocol Daemon (pppd),
which has a significant potential impact due to the possibility of remote code execution
prior to authentication.&lt;/p>
&lt;p>OpenWrt by default enables the _FORTIFY_SOURCE=1 compiler macro which introduces
additional checks to detect buffer-overflows in the standard library functions, thus
protecting the memcpy() abused in this overflow, preventing the actual buffer overflow
and hence possible remote code execution by instead terminating the pppd daemon. Due
to those defaults the impact of the issue was changed to a denial of service
vulnerability, which is now also addressed by this fix.&lt;/p></description></item><item><title>libubox tagged binary data JSON serialization vulnerability</title><link>https://openwrt.org/advisories/2020-01-31-2/</link><pubDate>Fri, 31 Jan 2020 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2020-01-31-2/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>Possibly exploitable vulnerability exists in the libubox library of OpenWrt,
specifically in the parts related to JSON conversion of tagged binary data,
so called blobs. An attacker could possibly exploit this behavior by
providing specially crafted binary blob or JSON which would then be translated
into blob internally.&lt;/p>
&lt;p>This malicious blobmsg input would contain blob attribute holding large enough
numeric value of type double which then processed by blobmsg_format_json would
overflow the buffer array designated for JSON output allocated on the stack.&lt;/p></description></item><item><title>Opkg susceptible to MITM</title><link>https://openwrt.org/advisories/2020-01-31-1/</link><pubDate>Fri, 31 Jan 2020 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2020-01-31-1/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>A bug in the package list parse logic of OpenWrt’s opkg fork caused the
package manager to ignore SHA-256 checksums embedded in the signed repository
index, effectively bypassing integrity checking of downloaded .ipk artifacts.&lt;/p>
&lt;p>The bug has been introduced with commit &lt;a href="https://git.openwrt.org/54cc7e3">https://git.openwrt.org/54cc7e3&lt;/a> which
failed to advance the proper string pointer when skipping the leading white-
space portition of the checksum string, causing the subsequent hex decoding
loop to return early with a zero length checksum.&lt;/p></description></item><item><title>uhttpd invalid data access via HTTP POST request</title><link>https://openwrt.org/advisories/2020-01-13-1/</link><pubDate>Mon, 13 Jan 2020 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2020-01-13-1/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>An invalid data access can be triggered with an HTTP POST request to a CGI
script specifying both &lt;code>Transfer-Encoding: chunked&lt;/code> and a large
&lt;code>Content-Length&lt;/code> which exceeds 2^31 and is interpreted as a signed negative
number.&lt;/p>
&lt;p>The negative content length is assigned to &lt;code>r-&amp;gt;content_length&lt;/code> in
&lt;code>client_parse_header&lt;/code> and passed as a negative read length to
&lt;code>ustream_consume&lt;/code> in &lt;code>client_poll_post_data&lt;/code> which will set the internal
ustream buffer pointer to an invalid address, causing out of bounds memory
reads later on in the code flow.&lt;/p></description></item><item><title>LuCI CSRF vulnerability</title><link>https://openwrt.org/advisories/2019-11-05-2/</link><pubDate>Tue, 05 Nov 2019 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2019-11-05-2/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>A logic flaw in LuCI‘s HTTP routing component led to ineffective CSRF
token testing for various request endpoints, specifically ones using
the ’‘arcombine()’’ dispatch action.&lt;/p>
&lt;p>This allows 3rd party web pages running in the same browser session
as an active LuCI login session to perform unintended operations on
the device without user intervention, such as changing firewall rules
or reconfiguring the network.&lt;/p>
&lt;h2 id="requirements">REQUIREMENTS&lt;/h2>
&lt;p>In order to exploit this vulnerability, a user needs to be logged into
LuCI while visiting malicious websites in the same browser session, e.g.
within a different tab.&lt;/p></description></item><item><title>LuCI stored XSS</title><link>https://openwrt.org/advisories/2019-11-05-1/</link><pubDate>Tue, 05 Nov 2019 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2019-11-05-1/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>A vulnerability has been reported in LuCI which allows injection of
script code through maliciously crafted wireless network SSIDs.&lt;/p>
&lt;p>When joining a wireless network by clicking Network -&amp;gt; Wireless -&amp;gt; Join,
the subsequent configuration view interprets the SSID of the network
to join without proper escaping, allowing to execute arbitrary
JavaScript in the client‘s web browser through network names which
contains payload, for example
’‘AP&amp;lt;/h2&amp;gt;&amp;lt;svg onclick=alert(0);&amp;gt;’’&lt;/p>
&lt;p>Additionally the network interface overview displays configured wireless
network SSID without proper escaping.&lt;/p></description></item><item><title>ustream-ssl information disclosure</title><link>https://openwrt.org/advisories/2019-11-05-3/</link><pubDate>Tue, 05 Nov 2019 00:00:00 +0000</pubDate><guid>https://openwrt.org/advisories/2019-11-05-3/</guid><description>&lt;h2 id="description">DESCRIPTION&lt;/h2>
&lt;p>An exploitable information leak vulnerability exists in the ustream-ssl
library of OpenWrt. When connecting to a remote server, the server’s
SSL certificate is checked but no action is taken when the certificate
is invalid. An attacker could exploit this behavior by performing a
man-in-the-middle attack, providing any certificate, leading to the
theft of all the data sent by the client during the first request.&lt;/p>
&lt;h2 id="requirements">REQUIREMENTS&lt;/h2>
&lt;p>In order to exploit this vulnerability, a malicious actor needs to
perform a man-in-the-middle attack, presenting a requesting ustream-ssl
client with any invalid certificate. The ustream-ssl client will
eventually tear down the SSL connection due to that, but only after
flushing pending data, e.g. the HTTP request payload in case of an
HTTPS client application.&lt;/p></description></item></channel></rss>