Repository navigation
Conversation
|
Closing this because the default configuration blocks the highlighted attack paths, and a rebuild picks up Alpine's updated packages without these version constraints. We don't enable |
|
Thanks for the quick review, and agreed on the analysis: with the default config none of these paths are reachable. Would you consider tagging a plain rebuild (e.g. |
|
I don't plan a release solely to clear scanner findings when the reported attack paths aren't exposed by the default configuration. We'll pick up the updated packages with the next release. |
|
Fair enough, thanks for taking the time to answer. We'll pick up the updated packages with the next release. |
The current
26.11.0image (26.11.0-r1) ships PHP 8.4.27 and nginx 1.30.6, which are both affected by recently disclosed vulnerabilities:Both fixed versions are already in Alpine 3.24 (
php848.4.28-r0 andnginx1.30.7-r0). Because the packages are not pinned, a plain rebuild would pick them up. This PR adds minimum version constraints onnginx,php84andphp84-fpm, so a build cannot silently produce an image with vulnerable packages, and it gives a commit to tag a26.11.0-r2release from.With the default configuration, the bundled nginx does not enable HTTP/2 and does not reuse FastCGI connections (
fastcgi_keep_conn), so the most severe issues are not exploitable out of the box. The fixed packages are still worth shipping.Tested by building the image locally: