Simplified or removed post_install

[nicholasdille]

Implements #5781

[github-actions]

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/porter:1.1.0

📦 Image Reference ghcr.io/uniget-org/tools/porter:1.1.0

digest	sha256:61693706f1bb462aabfa09ed1747e74718b0962fba37be30bb9519d49540c52f
vulnerabilities
platform	linux/amd64
size	21 MB
packages	205

stdlib 1.22.1 (golang) pkg:golang/[email protected] Affected range >=1.22.0-0 <1.22.4 Fixed version 1.22.4 Description The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms. Affected range >=1.22.0-0 <1.22.5 Fixed version 1.22.5 Description The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail. An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail. Affected range >=1.22.0-0 <1.22.4 Fixed version 1.22.4 Description The archive/zip package's handling of certain types of invalid zip files differs from the behavior of most zip implementations. This misalignment could be exploited to create an zip file with contents that vary depending on the implementation reading the file. The archive/zip package now rejects files containing these errors. Affected range >=1.22.0-0 <1.22.3 Fixed version 1.22.3 Description A malformed DNS message in response to a query can cause the Lookup functions to get stuck in an infinite loop. Affected range >=1.22.0-0 <1.22.2 Fixed version 1.22.2 Description An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send. The fix sets a limit on the amount of excess header frames we will process before closing a connection.

github.com/opencontainers/runc 1.1.12 (golang) pkg:golang/github.com/opencontainers/[email protected] OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities Affected range <1.2.0-rc.1 Fixed version 1.2.0-rc.1 CVSS Score 7.2 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Description Withdrawn Advisory This advisory has been withdrawn because it was incorrectly attributed to runc. Please see the issue here for more information. Original Description A flaw was found in cri-o, where an arbitrary systemd property can be injected via a Pod annotation. Any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system. This issue has its root in how runc handles Config Annotations lists.

google.golang.org/grpc 1.64.0 (golang) pkg:golang/google.golang.org/[email protected] Exposure of Sensitive Information to an Unauthorized Actor Affected range >=1.64.0 <1.64.1 Fixed version 1.64.1 Description Impact This issue represents a potential PII concern. If applications were printing or logging a context containing gRPC metadata, the affected versions will contain all the metadata, which may include private information. Patches The issue first appeared in 1.64.0 and is patched in 1.64.1 and 1.65.0 Workarounds If using an affected version and upgrading is not possible, ensuring you do not log or print contexts will avoid the problem.