See Security old for the old page.
This page lists the processes, tools and mechanisms OpenWrt uses to the security of OpenWrt. This covers the OpenWrt distribution with the official package feeds hosted at https://github.com/openwrt/ and also the OpenWrt specific tools hosted at https://git.openwrt.org/ like procd, ubus and libubox
This lists the currently support or not supported OpenWrt versions.
|Version||Current status||Projected EOL|
|19.07||Fully supported||Jan 2021|
|18.06||Security maintenance||Mai 2020|
|17.01||End of life||EOL|
|15.05||End of life||EOL|
The Version references the most recent stable version from this release branch.
The Projected EOL can be extended later, depending on the future situation, like the release date of the next release.
This only covers the core OpenWrt packages and not the external package feeds hosted on github. Some feed package maintainer do not take care of all OpenWrt versions where the the core components are still supported. For the best security support we suggest everyone to upgrade to the most recent stable version.
The OpenWrt project uses multiple tools to identify potential security problems. The information are normally available for everyone and we appreciate fixes for problems reported by these tools form everyone.
This report shows the version number of all packages from the base and the package repository and compares it against the recent upstream released versions. In addition the tool which generates this page also checks for existing CVEs assigned to the packages based on the Common Platform Enumeration (CPE) which is listed in the PKG_CPE_ID variable of many packages. This page is weekly regenerated for master and the active release branches. https://sdwalker.github.io/uscan/index.html
OpenWrt uses the commercial Coverity Scan tool which is available for free to open source projects to do static code analyses on the OpenWrt components. This scans one OpenWrt build per week and reports the problems found in the components developed in the OpenWrt project like procd and ubus, but not on (patched) third party components. https://scan.coverity.com/projects/openwrt
OpenWrt releases should be reproducible to make it possible to check that the releases we produced are really matching the source code we delivered and no backdoors were introduced in the build process. The reproducible builds project checks that OpenWrt master is still reproducible and publishes the results here: https://reproducible.debian.net/openwrt/openwrt.html
OpenWrt operates multiple build bot instances which are building snapshots of the master and the supported release branches. See Buildbot for details.
When a change to a package is committed to the OpenWrt base repository of package feed the build bots are automatically detection this change and will rebuild this package. The new newly build package can then be installed with opkg or be integrated with the image builder by users of OpenWrt. This allows us to ship updates in about 2 days to the end users.
The kernel is normally located in its own partition and upgrades are not so easily possible. Therefore this mechanism currently does not work for the kernel itself and kernel modules, there a new minor release is needed to ship fixes to end users.
OpenWrt activates some build hardening options at compile time for all packages build.
Source: config/Config-build.in. Note that individual packages and/or targets may ignore or otherwise not respect these settings.
|.config line||Enabled by Default?||Notes|
| ||Yes||Kernel config CONFIG_STACKPROTECTOR|
| ||Kernel config CONFIG_STACKPROTECTOR_STRONG|