Updating packages with vulnerabilities

[novda]

Motivation and context

How has this been tested?

Checklist

• I submit my changes into the develop branch
• I have created a changelog fragment
• I have updated the documentation accordingly
• I have added tests to cover my changes
• I have linked related issues (see GitHub docs)
• I have increased versions of npm packages if it is necessary
  (cvat-canvas,
  cvat-core,
  cvat-data and
  cvat-ui)

License

• I submit my code changes under the same MIT License that covers the project.
  Feel free to contact the maintainers if that's a concern.

[codecov]

Codecov Report

Merging #7713 (b036c8f) into develop (02889ee) will decrease coverage by 0.03%.
Report is 6 commits behind head on develop.
The diff coverage is n/a.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #7713      +/-   ##
===========================================
- Coverage    83.36%   83.33%   -0.03%     
===========================================
  Files          373      373              
  Lines        39722    39722              
  Branches      3747     3747              
===========================================
- Hits         33113    33104       -9     
- Misses        6609     6618       +9     

Components	Coverage Δ
cvat-ui	79.16% <ø> (-0.05%)	⬇️
cvat-server	87.21% <ø> (-0.01%)	⬇️

[nmanovic]

@novda , Could you please provide the docker scout output?

[bsekachev]

@novda Shall we update Pillow to 10.3?
Like in this PR, proposed by Snyk #7724 ?

[novda]

🔍 Vulnerabilities of cvat/server:dev

📦 Image Reference cvat/server:dev

digest	sha256:e26f2c7c8aaeaa3de4f3b722ad81e926314ecb8a75296e86f645c26bc7267058
vulnerabilities
platform	linux/arm64
size	436 MB
packages	479

golang.org/x/net 0.0.0-20200528225125-3c3fba18258b (golang) pkg:golang/golang.org/x/[email protected] Affected range <0.0.0-20220906165146-f3363e06e74c Fixed version 0.0.0-20220906165146-f3363e06e74c CVSS Score 7.5 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Description In net/http in Go before 1.18.6 and 1.19.x before 1.19.1, attackers can cause a denial of service because an HTTP/2 connection can hang during closing if shutdown were preempted by a fatal error. Affected range <0.0.0-20211209124913-491a49abca63 Fixed version 0.0.0-20211209124913-491a49abca63 Description An attacker can cause unbounded memory growth in servers accepting HTTP/2 requests. Loop with Unreachable Exit Condition ('Infinite Loop') Affected range <0.0.0-20210520170846-37e1c6afe023 Fixed version 0.0.0-20210520170846-37e1c6afe023 CVSS Score 7.5 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Description Go through 1.15.12 and 1.16.x through 1.16.4 has a golang.org/x/net/html infinite loop via crafted ParseFragment input.

golang.org/x/text 0.3.2 (golang) pkg:golang/golang.org/x/[email protected] Missing Release of Resource after Effective Lifetime Affected range <0.3.8 Fixed version 0.3.8 CVSS Score 7.5 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Description The BCP 47 tag parser has quadratic time complexity due to inherent aspects of its design. Since the parser is, by design, exposed to untrusted user input, this can be leveraged to force a program to consume significant time parsing Accept-Language headers. The parser cannot be easily rewritten to fix this behavior for various reasons. Instead the solution implemented in this CL is to limit the total complexity of tags passed into ParseAcceptLanguage by limiting the number of dashes in the string to 1000. This should be more than enough for the majority of real world use cases, where the number of tags being sent is likely to be in the single digits. Specific Go Packages Affected golang.org/x/text/language Out-of-bounds Read Affected range <0.3.7 Fixed version 0.3.7 CVSS Score 7.5 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Description golang.org/x/text/language in golang.org/x/text before 0.3.7 can panic with an out-of-bounds read during BCP 47 language tag parsing. Index calculation is mishandled. If parsing untrusted user input, this can be used as a vector for a denial-of-service attack.

stdlib 1.20.5 (golang) pkg:golang/[email protected] Affected range <1.20.10 Fixed version 1.20.10 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.

pip 22.0.2 (pypi) pkg:pypi/[email protected] OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities Affected range >=0 Fixed version Not Fixed CVSS Score 7.8 CVSS Vector CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Description An issue was discovered in pip (all versions) because it installs the version with the highest version number, even if the user had intended to obtain a private package from a private index. This only affects use of the --extra-index-url option, and exploitation requires that the package does not already exist in the public index (and thus the attacker can put the package there with an arbitrary version number).

redis 4.5.4 (pypi) pkg:pypi/[email protected] Affected range =4.5.4 Fixed version Not Fixed Description redis-7.0.10 was discovered to contain a segmentation violation.

setuptools 59.6.0 (pypi) pkg:pypi/[email protected] Inefficient Regular Expression Complexity Affected range <65.5.1 Fixed version 65.5.1 CVSS Score 7.5 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Description Python Packaging Authority (PyPA)'s setuptools is a library designed to facilitate packaging Python projects. Setuptools version 65.5.0 and earlier could allow remote attackers to cause a denial of service by fetching malicious HTML from a PyPI package or custom PackageIndex page due to a vulnerable Regular Expression in package_index. This has been patched in version 65.5.1.

What's Next?
View base image update recommendations → docker scout recommendations cvat/server:dev

🔍 Vulnerabilities of openpolicyagent/opa:0.63.0

📦 Image Reference openpolicyagent/opa:0.63.0

digest	sha256:593445863d9ea091af8c5a9c4d6d913f0a6982158c521a087c5a9c7379abb8ac
vulnerabilities
platform	linux/amd64
size	36 MB
packages	93

🔍 Vulnerabilities of postgres:15-alpine

📦 Image Reference postgres:15-alpine

digest	sha256:4d4cbd1ce7920501adc5c257467b6bade5252e83fd94c8788e66e189c3137dbc
vulnerabilities
platform	linux/arm64
size	104 MB
packages	64

🔍 Vulnerabilities of apache/kvrocks:2.7.0

📦 Image Reference apache/kvrocks:2.7.0

digest	sha256:ef467e036d6c773c929a89605b53eaf551cefcfe7f404157f22733a63a8b8493
vulnerabilities
platform	linux/arm64
size	18 MB
packages	19

🔍 Vulnerabilities of redis:7.2.3-alpine

📦 Image Reference redis:7.2.3-alpine

digest	sha256:32d600912a196d68de54062c2d8fbe6c34a07024a8747189cafd30365925cb43
vulnerabilities
platform	linux/arm64
size	18 MB
packages	27

stdlib 1.18.2 (golang) pkg:golang/[email protected] Affected range <1.19.9 Fixed version 1.19.9 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 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 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 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.20.0 Fixed version 1.20.0 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.10 Fixed version 1.20.10 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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.

What's Next?
View base image update recommendations → docker scout recommendations redis:7.2.3-alpine

[SpecLad]

A few points here:

• There should be an equivalent change to the Helm chart.

• I'm pretty sure we mention the supported version of Nuclio in the documentation somewhere. Please check and update it there.

• The gap between 1.11.24 and 1.13.0 is fairly large. I think you should try every serverless function and make sure they still work with the new Nuclio version.

[novda]

name	updates
cvat_server	Pillow:10.1.0 -> 10.3.0 Django:4.2.1 -> 4.2.7
nuclio	nuclio/dashboard:1.11.24 -> 1.13.0 (will be updated in another pr)
cvat_opa	openpolicyagent/opa:0.45.0-rootless -> 0.63.0