According to [1] the ESI feature implementation in squid is vulnerable without any fix available. NVD says it's fixed in 6.10, however the change in this release only disables ESI by default (which we always did via PACKAGECONFIG). Commit in master branch related to this CVE is [2]. Title is "Remove Edge Side Include (ESI) protocol" and it's also what it does. So there will never be a fix for these ESI vulnerabilities. We should not break features in LTS branch and cannot fix this problem. So ignrore this CVE based on set PACKAGECONFIG which should remove it from reports for most users. Thos who need ESI need to assess the risk themselves. [1] https://github.com/squid-cache/squid/security/advisories/GHSA-f975-v7qw-q7hj [2] https://github.com/squid-cache/squid/commit/5eb89ef3d828caa5fc43cd8064f958010dbc8158 Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Armin Kuster <akuster808@gmail.com>
meta-networking
This layer is intended to be a central point for networking-related packages and configuration. It should be useful directly on top of oe-core and compliments meta-openembedded. It should be primarily useful to the following groups:
- Anyone building a small networking device (eg. a home router /
bridge / switch).
- Anyone wanting to add network services to their device (eg.
anything that might benefit from a small ftp/tftp server)
Dependencies
This layer depends on:
URI: git://git.openembedded.org/openembedded-core branch: Scarthgap
For some recipes, the meta-oe layer is required:
URI: git://git.openembedded.org/meta-openembedded subdirectory: meta-oe branch: Scarthgap
URI: git://git.openembedded.org/meta-openembedded subdirectory: meta-python branch: Scarthgap
Maintenance
Stable Layer maintainer: Armin Kuster akuster808@gmail.com
Please see the MAINTAINERS file for information on contacting the maintainers of this layer, as well as instructions for submitting patches.