Add research-vuln-scan workflow

[robert-schardt]

What

Compare different tools for scanning docker images for CVE's.

Why

We want to use the best CVE scanner for our docker images: https://jira.greenbone.net/browse/DEVOPS-1249

References

https://jira.greenbone.net/browse/DEVOPS-1249

Checklist

• Comparison list: https://confluence.greenbone.net/display/~robert.schardt/Research+-+Container+image+security+scanners

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[robert-schardt]

The rate limit of the github authentication makes it really flaky to run this workflow: https://github.com/greenbone/opensight-postgres/actions/runs/11664302625/job/32476582882

[github-actions]

🔍 Vulnerabilities of harbor-os.greenbone.net/opensight/opensight-postgres:16

📦 Image Reference harbor-os.greenbone.net/opensight/opensight-postgres:16

digest	sha256:e7473aca2e54371661cea55d6a08c855aba7b065a7591e7841b88f8ce383f13d
vulnerabilities
size	154 MB
packages	205

📦 Base Image debian:12-slim

also known as	12.8-slim bookworm-20241111-slim bookworm-slim
digest	sha256:c00d13c9aa5d1acfa44e5ababbb8d1f5ac53fa94bc2f993070ccea2dcaf5aa64
vulnerabilities

stdlib 1.18.2 (golang) pkg:golang/[email protected] # Dockerfile (2:2) FROM postgres:${POSTGRES_VERSION} Affected range <1.21.11 Fixed version 1.21.11 EPSS Score 0.06% EPSS Percentile 29th percentile 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.19.9 Fixed version 1.19.9 EPSS Score 0.28% EPSS Percentile 69th percentile Description Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution. Affected range <1.19.8 Fixed version 1.19.8 EPSS Score 0.86% EPSS Percentile 83rd percentile Description Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml. With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21. Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution. Affected range <1.19.10 Fixed version 1.19.10 EPSS Score 0.09% EPSS Percentile 40th percentile Description On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors. If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers. Affected range >=1.18.0-0 <1.18.3 Fixed version 1.18.3 EPSS Score 0.04% EPSS Percentile 16th percentile Description On Windows, executing Cmd.Run, Cmd.Start, Cmd.Output, or Cmd.CombinedOutput when Cmd.Path is unset will unintentionally trigger execution of any binaries in the working directory named either "..com" or "..exe". Affected range <1.22.7 Fixed version 1.22.7 EPSS Score 0.04% EPSS Percentile 17th percentile Description Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion. Affected range <1.22.7 Fixed version 1.22.7 EPSS Score 0.04% EPSS Percentile 17th percentile Description Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635. Affected range <1.21.12 Fixed version 1.21.12 EPSS Score 0.04% EPSS Percentile 17th percentile 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.21.8 Fixed version 1.21.8 EPSS Score 0.04% EPSS Percentile 12th percentile Description The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers. Affected range <1.21.9 Fixed version 1.21.9 EPSS Score 0.04% EPSS Percentile 15th percentile 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. Affected range <1.20.0 Fixed version 1.20.0 EPSS Score 0.08% EPSS Percentile 36th percentile Description Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits. In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels. Affected range <1.20.11 Fixed version 1.20.11 EPSS Score 0.17% EPSS Percentile 55th percentile Description The filepath package does not recognize paths with a ??\ prefix as special. On Windows, a path beginning with ??\ is a Root Local Device path equivalent to a path beginning with \?. Paths with a ??\ prefix may be used to access arbitrary locations on the system. For example, the path ??\c:\x is equivalent to the more common path c:\x. Before fix, Clean could convert a rooted path such as \a..??\b into the root local device path ??\b. Clean will now convert this to .??\b. Similarly, Join(, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path ??\b. Join will now convert this to .??\b. In addition, with fix, IsAbs now correctly reports paths beginning with ??\ as absolute, and VolumeName correctly reports the ??\ prefix as a volume name. UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with ?, resulting in filepath.Clean(?\c:) returning ?\c: rather than ?\c:\ (among other effects). The previous behavior has been restored. Affected range <1.20.10 Fixed version 1.20.10 EPSS Score 83.78% EPSS Percentile 99th percentile Description A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing. With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection. This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2. The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function. Affected range <1.20.10 Fixed version 1.20.10 EPSS Score 0.36% EPSS Percentile 73rd percentile Description A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing. With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection. This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2. The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function. Affected range <1.19.8 Fixed version 1.19.8 EPSS Score 0.20% EPSS Percentile 58th percentile Description Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow. Affected range <1.19.8 Fixed version 1.19.8 EPSS Score 0.96% EPSS Percentile 84th percentile Description Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector. The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms: Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=. Affected range <1.19.8 Fixed version 1.19.8 EPSS Score 0.41% EPSS Percentile 75th percentile Description HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service. Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service. With fix, header parsing now correctly allocates only the memory required to hold parsed headers. Affected range <1.19.6 Fixed version 1.19.6 EPSS Score 0.21% EPSS Percentile 60th percentile Description A denial of service is possible from excessive resource consumption in net/http and mime/multipart. Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files. With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous. In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct. Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader. Affected range <1.19.6 Fixed version 1.19.6 EPSS Score 0.20% EPSS Percentile 59th percentile Description Large handshake records may cause panics in crypto/tls. Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses. This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert). Affected range <1.19.6 Fixed version 1.19.6 EPSS Score 4.18% EPSS Percentile 92nd percentile Description A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests. Affected range <1.19.6 Fixed version 1.19.6 EPSS Score 0.17% EPSS Percentile 55th percentile Description A path traversal vulnerability exists in filepath.Clean on Windows. On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack. After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b". Affected range <1.18.9 Fixed version 1.18.9 EPSS Score 0.16% EPSS Percentile 54th percentile Description On Windows, restricted files can be accessed via os.DirFS and http.Dir. The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access. In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system. With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error. Affected range <1.18.8 Fixed version 1.18.8 EPSS Score 0.10% EPSS Percentile 43rd percentile Description Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows. In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D". Affected range <1.18.7 Fixed version 1.18.7 EPSS Score 0.22% EPSS Percentile 61st percentile Description Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service. The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory. After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected. Affected range >=1.18.0-0 <1.18.5 Fixed version 1.18.5 EPSS Score 0.19% EPSS Percentile 58th percentile Description Decoding big.Float and big.Rat types can panic if the encoded message is too short, potentially allowing a denial of service. Affected range >=1.18.0-0 <1.18.4 Fixed version 1.18.4 EPSS Score 0.19% EPSS Percentile 57th percentile Description Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. Affected range >=1.18.0-0 <1.18.3 Fixed version 1.18.3 EPSS Score 0.15% EPSS Percentile 53rd percentile Description On Windows, rand.Read will hang indefinitely if passed a buffer larger than 1 << 32 - 1 bytes. Affected range >=1.18.0-0 <1.18.4 Fixed version 1.18.4 EPSS Score 0.19% EPSS Percentile 57th percentile Description Unmarshaling an XML document into a Go struct which has a nested field that uses the 'any' field tag can panic due to stack exhaustion. Affected range >=1.18.0-0 <1.18.4 Fixed version 1.18.4 EPSS Score 0.19% EPSS Percentile 57th percentile Description Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion. Affected range >=1.18.0-0 <1.18.4 Fixed version 1.18.4 EPSS Score 0.19% EPSS Percentile 57th percentile Description Calling Reader.Read on an archive containing a large number of concatenated 0-length compressed files can cause a panic due to stack exhaustion. Affected range >=1.18.0-0 <1.18.4 Fixed version 1.18.4 EPSS Score 0.19% EPSS Percentile 57th percentile Description Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion. Affected range >=1.18.0-0 <1.18.3 Fixed version 1.18.3 EPSS Score 0.16% EPSS Percentile 54th percentile Description On Windows, the filepath.Clean function can convert certain invalid paths to valid, absolute paths, potentially allowing a directory traversal attack. For example, Clean(".\c:") returns "c:". Affected range <1.18.7 Fixed version 1.18.7 EPSS Score 0.16% EPSS Percentile 53rd percentile Description Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value. After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged. Affected range <1.18.7 Fixed version 1.18.7 EPSS Score 0.21% EPSS Percentile 59th percentile Description Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB. Affected range >=1.18.0-0 <1.18.4 Fixed version 1.18.4 EPSS Score 0.19% EPSS Percentile 57th percentile Description Calling Decoder.Skip when parsing a deeply nested XML document can cause a panic due to stack exhaustion. Affected range <1.18.6 Fixed version 1.18.6 EPSS Score 0.24% EPSS Percentile 63rd percentile Description HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service. Affected range <1.19.9 Fixed version 1.19.9 EPSS Score 0.15% EPSS Percentile 52nd percentile Description Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags. Affected range <1.19.9 Fixed version 1.19.9 EPSS Score 0.15% EPSS Percentile 52nd percentile Description Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input. Affected range <1.21.8 Fixed version 1.21.8 EPSS Score 0.04% EPSS Percentile 12th percentile Description When parsing a multipart form (either explicitly with Request.ParseMultipartForm or implicitly with Request.FormValue, Request.PostFormValue, or Request.FormFile), limits on the total size of the parsed form were not applied to the memory consumed while reading a single form line. This permits a maliciously crafted input containing very long lines to cause allocation of arbitrarily large amounts of memory, potentially leading to memory exhaustion. With fix, the ParseMultipartForm function now correctly limits the maximum size of form lines. Affected range <1.19.11 Fixed version 1.19.11 EPSS Score 0.14% EPSS Percentile 51st percentile Description The HTTP/1 client does not fully validate the contents of the Host header. A maliciously crafted Host header can inject additional headers or entire requests. With fix, the HTTP/1 client now refuses to send requests containing an invalid Request.Host or Request.URL.Host value. Affected range >=1.18.0-0 <1.18.4 Fixed version 1.18.4 EPSS Score 0.16% EPSS Percentile 53rd percentile Description Client IP adresses may be unintentionally exposed via X-Forwarded-For headers. When httputil.ReverseProxy.ServeHTTP is called with a Request.Header map containing a nil value for the X-Forwarded-For header, ReverseProxy sets the client IP as the value of the X-Forwarded-For header, contrary to its documentation. In the more usual case where a Director function sets the X-Forwarded-For header value to nil, ReverseProxy leaves the header unmodified as expected. Affected range >=1.18.0-0 <1.18.4 Fixed version 1.18.4 EPSS Score 0.21% EPSS Percentile 59th percentile Description The HTTP/1 client accepted some invalid Transfer-Encoding headers as indicating a "chunked" encoding. This could potentially allow for request smuggling, but only if combined with an intermediate server that also improperly failed to reject the header as invalid. Affected range <1.20.8 Fixed version 1.20.8 EPSS Score 0.11% EPSS Percentile 46th percentile Description The html/template package does not apply the proper rules for handling occurrences of "<script", "<!--", and "</script" within JS literals in <script> contexts. This may cause the template parser to improperly consider script contexts to be terminated early, causing actions to be improperly escaped. This could be leveraged to perform an XSS attack. Affected range <1.20.8 Fixed version 1.20.8 EPSS Score 0.15% EPSS Percentile 52nd percentile Description The html/template package does not properly handle HTML-like "" comment tokens, nor hashbang "#!" comment tokens, in <script> contexts. This may cause the template parser to improperly interpret the contents of <script> contexts, causing actions to be improperly escaped. This may be leveraged to perform an XSS attack. Affected range <1.21.8 Fixed version 1.21.8 EPSS Score 0.04% EPSS Percentile 12th percentile Description Verifying a certificate chain which contains a certificate with an unknown public key algorithm will cause Certificate.Verify to panic. This affects all crypto/tls clients, and servers that set Config.ClientAuth to VerifyClientCertIfGiven or RequireAndVerifyClientCert. The default behavior is for TLS servers to not verify client certificates. Affected range <1.21.11 Fixed version 1.21.11 EPSS Score 0.04% EPSS Percentile 11th percentile 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.18.0-0 <1.18.4 Fixed version 1.18.4 EPSS Score 0.08% EPSS Percentile 34th percentile Description Calling any of the Parse functions on Go source code which contains deeply nested types or declarations can cause a panic due to stack exhaustion. Affected range <1.20.11 Fixed version 1.20.11 EPSS Score 0.08% EPSS Percentile 35th percentile Description On Windows, The IsLocal function does not correctly detect reserved device names in some cases. Reserved names followed by spaces, such as "COM1 ", and reserved names "COM" and "LPT" followed by superscript 1, 2, or 3, are incorrectly reported as local. With fix, IsLocal now correctly reports these names as non-local. Affected range <1.20.12 Fixed version 1.20.12 EPSS Score 0.06% EPSS Percentile 27th percentile Description A malicious HTTP sender can use chunk extensions to cause a receiver reading from a request or response body to read many more bytes from the network than are in the body. A malicious HTTP client can further exploit this to cause a server to automatically read a large amount of data (up to about 1GiB) when a handler fails to read the entire body of a request. Chunk extensions are a little-used HTTP feature which permit including additional metadata in a request or response body sent using the chunked encoding. The net/http chunked encoding reader discards this metadata. A sender can exploit this by inserting a large metadata segment with each byte transferred. The chunk reader now produces an error if the ratio of real body to encoded bytes grows too small. Affected range <1.19.12 Fixed version 1.19.12 EPSS Score 0.12% EPSS Percentile 48th percentile Description Extremely large RSA keys in certificate chains can cause a client/server to expend significant CPU time verifying signatures. With fix, the size of RSA keys transmitted during handshakes is restricted to <= 8192 bits. Based on a survey of publicly trusted RSA keys, there are currently only three certificates in circulation with keys larger than this, and all three appear to be test certificates that are not actively deployed. It is possible there are larger keys in use in private PKIs, but we target the web PKI, so causing breakage here in the interests of increasing the default safety of users of crypto/tls seems reasonable. Affected range <1.19.7 Fixed version 1.19.7 EPSS Score 0.10% EPSS Percentile 43rd percentile Description The ScalarMult and ScalarBaseMult methods of the P256 Curve may return an incorrect result if called with some specific unreduced scalars (a scalar larger than the order of the curve). This does not impact usages of crypto/ecdsa or crypto/ecdh. Affected range <1.18.9 Fixed version 1.18.9 EPSS Score 0.29% EPSS Percentile 70th percentile Description An attacker can cause excessive memory growth in a Go server accepting HTTP/2 requests. HTTP/2 server connections contain a cache of HTTP header keys sent by the client. While the total number of entries in this cache is capped, an attacker sending very large keys can cause the server to allocate approximately 64 MiB per open connection. Affected range <1.22.7 Fixed version 1.22.7 EPSS Score 0.04% EPSS Percentile 17th percentile Description Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion. Affected range <1.21.8 Fixed version 1.21.8 EPSS Score 0.04% EPSS Percentile 12th percentile Description When following an HTTP redirect to a domain which is not a subdomain match or exact match of the initial domain, an http.Client does not forward sensitive headers such as "Authorization" or "Cookie". For example, a redirect from foo.com to www.foo.com will forward the Authorization header, but a redirect to bar.com will not. A maliciously crafted HTTP redirect could cause sensitive headers to be unexpectedly forwarded.

[github-actions]

Recommended fixes for image greenbone/opensight-postgres:4c543c29bee4484992a892ef78949ba9d2a8d7d4

Base image is debian:12-slim

Name	bookworm-20241111-slim
Digest	sha256:c00d13c9aa5d1acfa44e5ababbb8d1f5ac53fa94bc2f993070ccea2dcaf5aa64
Vulnerabilities
Pushed	1 week ago
Size	29 MB
Packages	125
Flavor	debian
OS	12
Slim	✅

The base image is also available under the supported tag(s): 12.8-slim, bookworm-20241111-slim, bookworm-slim

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

Tag	Details	Pushed	Vulnerabilities
stable-slim Tag is preferred tag Also known as: stable-20241111-slim	Benefits: Same OS detected Tag is preferred tag Image has similar size Image has same number of vulnerabilities Image contains equal number of packages Tag is using slim variant stable-slim was pulled 46K times last month Image details: Size: 29 MB Flavor: debian OS: 12 Slim: ✅	1 week ago
12 Tag is latest Also known as: 12.8 bookworm bookworm-20241111 latest	Benefits: Same OS detected Tag is latest Image has same number of vulnerabilities Image contains equal number of packages Image details: Size: 50 MB Flavor: debian OS: 12	1 week ago

[github-actions]

Overview

Image reference	greenbone/opensight-postgres:4c543c29bee4484992a892ef78949ba9d2a8d7d4	greenbone/opensight-postgres:4c543c29bee4484992a892ef78949ba9d2a8d7d4
- digest	30a563de922f	30a563de922f
- tag	4c543c29bee4484992a892ef78949ba9d2a8d7d4	4c543c29bee4484992a892ef78949ba9d2a8d7d4
- vulnerabilities
- platform	linux/amd64	linux/amd64
- size	174 MB	174 MB
- packages	205	205
Base Image	debian:12-slim also known as: • 12.8-slim • bookworm-20241111-slim • bookworm-slim	debian:12-slim also known as: • 12.8-slim • bookworm-20241111-slim • bookworm-slim
- vulnerabilities

[robert-schardt]

docker-scout action has too much locations in its sarif file:
"Error: Code Scanning could not process the submitted SARIF file:
rejecting SARIF, as there are more related locations per result than allowed (2243 > 1000)"
Update: ignoring unexpected and low severities fixes this

[y0urself]

Due to our switch to self-hosted registry, we would need to switch to self-hosted runner and adjust the image location in the workflow.
Afterwards I would merge the changes ...!

[robert-schardt]

Due to our switch to self-hosted registry, we would need to switch to self-hosted runner and adjust the image location in the workflow. Afterwards I would merge the changes ...!

Now the image should be fetched from harbor(prebuilt by the push.yml workflow) and it's updated to run on self-hosted-generic.