Hauke Mehrtens
a5c8be7fd4
ead-client trusts several length and index fields taken straight from the network when handling server responses, before authentication has completed. Since the client sends its requests as UDP broadcasts and never validates the origin of the replies, any host on the same L2 segment can spoof the whole handshake and hit these paths. handle_prime() copies sb->len bytes into saltbuf[MAXSALTLEN] (32 bytes) without checking the length, and passes sb->prime to t_getpreparam() without a range check. Both come from the wire, so a salt length up to 255 overflows saltbuf and a prime index up to 255 reads (and writes) out of bounds in the precompiled parameter table. This is GHSA-mq4v-mf82-24rr. handle_b() computes the copy length as msg->len - sizeof(number) and memcpy()s it into bbuf[MAXPARAMLEN] with no bounds check. msg->len is attacker controlled and only capped by the 1500 byte receive buffer, so up to 1479 bytes land in the 256 byte bbuf. A msg->len of 0 makes the signed length -1, which memcpy() treats as SIZE_MAX. This is GHSA-8f8g-5c8x-8mhh. handle_pong() writes the NUL terminator at pong->name[len] using an unchecked length, allowing a one byte write past msgbuf, and the receive loop's length check could wrap for a large msg->len. Bound every length against its destination buffer and range check the prime index, mirroring the checks already present on the daemon side in ead.c (handle_send_a(), commit63c0767f3d). ead-client is not installed into images by the ead package, only the daemon is, so this only affects administrators who build and run the client by hand. Link: https://github.com/openwrt/openwrt/security/advisories/GHSA-mq4v-mf82-24rr Link: https://github.com/openwrt/openwrt/security/advisories/GHSA-8f8g-5c8x-8mhh Fixes:2d86ea2a1d("add the 'ead' package (emergency access daemon), which can provide remote access to your device, even if the ip and firewall settings are broken") Assisted-by: Claude:claude-opus-4-8 Link: https://github.com/openwrt/openwrt/pull/25492 (cherry picked from commitb2cca02d47) Link: https://github.com/openwrt/openwrt/pull/25610 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.
Sunshine!
Download
Built firmware images are available for many architectures and come with a package selection to be used as WiFi home router. To quickly find a factory image usable to migrate from a vendor stock firmware to OpenWrt, try the Firmware Selector.
If your device is supported, please follow the Info link to see install instructions or consult the support resources listed below.
An advanced user may require additional or specific package. (Toolchain, SDK, ...) For everything else than simple firmware download, try the wiki download page:
Development
To build your own firmware you need a GNU/Linux, BSD or macOS system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.
Requirements
You need the following tools to compile OpenWrt, the package names vary between distributions. A complete list with distribution specific packages is found in the Build System Setup documentation.
binutils bzip2 diff find flex gawk gcc-6+ getopt grep install libc-dev libz-dev
make4.1+ perl python3.7+ rsync subversion unzip which
Quickstart
-
Run
./scripts/feeds update -ato obtain all the latest package definitions defined in feeds.conf / feeds.conf.default -
Run
./scripts/feeds install -ato install symlinks for all obtained packages into package/feeds/ -
Run
make menuconfigto select your preferred configuration for the toolchain, target system & firmware packages. -
Run
maketo build your firmware. This will download all sources, build the cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen applications for your target system.
Related Repositories
The main repository uses multiple sub-repositories to manage packages of
different categories. All packages are installed via the OpenWrt package
manager called opkg. If you're looking to develop the web interface or port
packages to OpenWrt, please find the fitting repository below.
-
LuCI Web Interface: Modern and modular interface to control the device via a web browser.
-
OpenWrt Packages: Community repository of ported packages.
-
OpenWrt Routing: Packages specifically focused on (mesh) routing.
-
OpenWrt Video: Packages specifically focused on display servers and clients (Xorg and Wayland).
Support Information
For a list of supported devices see the OpenWrt Hardware Database
Documentation
Support Community
- Forum: For usage, projects, discussions and hardware advise.
- Support Chat: Channel
#openwrton oftc.net.
Developer Community
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
#openwrt-develon oftc.net.
License
OpenWrt is licensed under GPL-2.0