You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This image/ project is based on acmesh-official/acme.sh which had a CVE with possible RCE 2 days ago, already exploited by the (former) chinese CA 'HiCA' (The issue is very entertaining to read btw 😏).
requires not removing the path from the acme url anymore as in version
3.0.0 acme.sh removed the special handling of the 'directory' path in
the url and just keeps the path as is, so acme-companion needs to do
the same
see acmesh-official/acme.sh@593e8e1Fixesnginx-proxy#1035
Bug description
This image/ project is based on acmesh-official/acme.sh which had a CVE with possible RCE 2 days ago, already exploited by the (former) chinese CA 'HiCA' (The issue is very entertaining to read btw 😏).
To be sure I've executed:
I have not tested if a RCE is possible though.
Solution:
That should be all, but I don't know since I'm not involved in this project.
acme-companion image version
nginx-proxy's Docker configuration, rendered nginx configuration, Containers logs, Docker host
N/A
The text was updated successfully, but these errors were encountered: