• 8.2-fpm-alpine
• 8.2-fpm-alpine3.22
• 8.2.29-fpm-alpine
• 8.2.29-fpm-alpine3.22

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:golang/stdlib@1.24.3

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

• 8.1-alpine3.21
• 8.1-cli-alpine
• 8.1-cli-alpine3.21
• 8.1.33-alpine
• 8.1.33-alpine3.21
• 8.1.33-cli-alpine
• 8.1.33-cli-alpine3.21
• 84499e7665570bbef8ca20d15c642d8d9485a887d6be7a8b335ca33b5d3126f0

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

• 8.3.24-fpm-alpine
• 8.3.24-fpm-alpine3.22
• 8.3-fpm-alpine3.22

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 33 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.3.24

• 8.4.11-fpm-alpine
• 8.4.11-fpm-alpine3.22
• 8.4-fpm-alpine3.22
• 8-fpm-alpine
• 8-fpm-alpine3.22
• fpm-alpine
• fpm-alpine3.22

• Same OS detected
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 37 MB
• Flavor: alpine
• OS: 3.22

• 8.2-alpine3.22
• 8.2-cli-alpine
• 8.2-cli-alpine3.22
• 8.2.29-alpine
• 8.2.29-alpine3.22
• 8.2.29-cli-alpine
• 8.2.29-cli-alpine3.22
• d8f4974194fb8fae35528e5ff3f03ca3566ee2e502f953b7817e0cbefebf8a0d

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:golang/stdlib@1.24.3

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

• 8.2-alpine3.22
• 8.2-cli-alpine
• 8.2-cli-alpine3.22
• 8.2.29-alpine
• 8.2.29-alpine3.22
• 8.2.29-cli-alpine
• 8.2.29-cli-alpine3.22
• d8f4974194fb8fae35528e5ff3f03ca3566ee2e502f953b7817e0cbefebf8a0d

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:golang/stdlib@1.24.3

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

• 8.1.33-cli-alpine3.22
• 8.1-cli-alpine3.22
• 8.1.33-alpine3.22

• Patch runtime version update
• Same OS detected
• Image has similar size
• Image has same number of vulnerabilities
• Image contains similar number of packages

• Size: 36 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.1.33

• 8.4.11-cli-alpine
• 8.4.11-cli-alpine3.22
• 8.4-cli-alpine
• 8.4-cli-alpine3.22
• 8-cli-alpine
• 8-cli-alpine3.22
• cli-alpine
• cli-alpine3.22
• alpine
• alpine3.22
• 8.4.11-alpine
• 8.4.11-alpine3.22
• 8.4-alpine3.22
• 8-alpine
• 8-alpine3.22

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains similar number of packages

• Size: 42 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.4.11

• 8.4.11-cli-alpine3.21
• 8.4-cli-alpine3.21
• 8-cli-alpine3.21
• cli-alpine3.21
• alpine3.21
• 8.4.11-alpine3.21
• 8-alpine3.21

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 42 MB
• Flavor: alpine
• OS: 3.21
• Runtime: 8.4.11

• 8.3.24-cli-alpine
• 8.3.24-cli-alpine3.22
• 8.3-cli-alpine
• 8.3-cli-alpine3.22
• 8.3.24-alpine
• 8.3.24-alpine3.22
• 8.3-alpine3.22

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains similar number of packages

• Size: 37 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.3.24

• 8.3.24-cli-alpine3.21
• 8.3-cli-alpine3.21
• 8.3.24-alpine3.21

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 37 MB
• Flavor: alpine
• OS: 3.21
• Runtime: 8.3.24

• 8.2.29-cli-alpine
• 8.2.29-cli-alpine3.22
• 8.2-cli-alpine
• 8.2-cli-alpine3.22
• 8.2.29-alpine
• 8.2.29-alpine3.22
• 8.2-alpine3.22

• Same OS detected
• Minor runtime version update
• Image has similar size
• Image has same number of vulnerabilities
• Image contains similar number of packages
• 8.2-alpine was pulled 1.8K times last month

• Size: 37 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.2.29

• 8.2.29-cli-alpine3.21
• 8.2-cli-alpine3.21
• 8.2.29-alpine3.21

• Same OS detected
• Minor runtime version update
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 36 MB
• Flavor: alpine
• OS: 3.21
• Runtime: 8.2.29

• 8.3-alpine3.22
• 8.3-cli-alpine
• 8.3-cli-alpine3.22
• 8.3.24-alpine
• 8.3.24-alpine3.22
• 8.3.24-cli-alpine
• 8.3.24-cli-alpine3.22
• b026e7d2fc6d7801e1af55dc42c7409b2f38d6b42c32494e9276b6ef40a28ee3

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:golang/stdlib@1.24.3

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

• 8.3-alpine3.22
• 8.3-cli-alpine
• 8.3-cli-alpine3.22
• 8.3.24-alpine
• 8.3.24-alpine3.22
• 8.3.24-cli-alpine
• 8.3.24-cli-alpine3.22
• b026e7d2fc6d7801e1af55dc42c7409b2f38d6b42c32494e9276b6ef40a28ee3

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:golang/stdlib@1.24.3

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

• 8.1-alpine3.21
• 8.1-cli-alpine
• 8.1-cli-alpine3.21
• 8.1.33-alpine
• 8.1.33-alpine3.21
• 8.1.33-cli-alpine
• 8.1.33-cli-alpine3.21
• 84499e7665570bbef8ca20d15c642d8d9485a887d6be7a8b335ca33b5d3126f0

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:pypi/setuptools@70.3.0

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Summary

A path traversal vulnerability in PackageIndex was fixed in setuptools version 78.1.1

Details

    def _download_url(self, url, tmpdir):
        # Determine download filename
        #
        name, _fragment = egg_info_for_url(url)
        if name:
            while '..' in name:
                name = name.replace('..', '.').replace('\\', '_')
        else:
            name = "__downloaded__"  # default if URL has no path contents

        if name.endswith('.[egg.zip](http://egg.zip/)'):
            name = name[:-4]  # strip the extra .zip before download

 -->       filename = os.path.join(tmpdir, name)

Here: https://github.com/pypa/setuptools/blob/6ead555c5fb29bc57fe6105b1bffc163f56fd558/setuptools/package_index.py#L810C1-L825C88

os.path.join() discards the first argument tmpdir if the second begins with a slash or drive letter.
name is derived from a URL without sufficient sanitization. While there is some attempt to sanitize by replacing instances of '..' with '.', it is insufficient.

Risk Assessment

As easy_install and package_index are deprecated, the exploitation surface is reduced.
However, it seems this could be exploited in a similar fashion like GHSA-r9hx-vwmv-q579, and as described by POC 4 in GHSA-cx63-2mw6-8hw5 report: via malicious URLs present on the pages of a package index.

Impact

An attacker would be allowed to write files to arbitrary locations on the filesystem with the permissions of the process running the Python code, which could escalate to RCE depending on the context.

References

https://huntr.com/bounties/d6362117-ad57-4e83-951f-b8141c6e7ca5
pypa/setuptools#4946

• 8.4.11-cli-alpine
• 8.4.11-cli-alpine3.22
• 8.4-cli-alpine
• 8.4-cli-alpine3.22
• 8-cli-alpine
• 8-cli-alpine3.22
• cli-alpine
• cli-alpine3.22
• alpine
• alpine3.22
• 8.4.11-alpine
• 8.4.11-alpine3.22
• 8.4-alpine3.22
• 8-alpine
• 8-alpine3.22

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 42 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.4.11

• 8.3.24-cli-alpine
• 8.3.24-cli-alpine3.22
• 8.3-cli-alpine
• 8.3-cli-alpine3.22
• 8.3.24-alpine
• 8.3.24-alpine3.22
• 8.3-alpine3.22

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 37 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.3.24

• 8.4.11-cli-alpine
• 8.4.11-cli-alpine3.22
• 8.4-cli-alpine
• 8.4-cli-alpine3.22
• 8-cli-alpine
• 8-cli-alpine3.22
• cli-alpine
• cli-alpine3.22
• alpine
• alpine3.22
• 8.4.11-alpine
• 8.4.11-alpine3.22
• 8.4-alpine3.22
• 8-alpine
• 8-alpine3.22

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 42 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.4.11

• 8.3.24-cli-alpine
• 8.3.24-cli-alpine3.22
• 8.3-cli-alpine
• 8.3-cli-alpine3.22
• 8.3.24-alpine
• 8.3.24-alpine3.22
• 8.3-alpine3.22

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 37 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.3.24

• 8.1-fpm-alpine3.21
• 8.1.33-fpm-alpine
• 8.1.33-fpm-alpine3.21
• da3eabe89d0c6c833838e3480d063d65f38577bc37dc976948b9352f3fb3d2fb

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

• 8.4.11-cli-alpine
• 8.4.11-cli-alpine3.22
• 8.4-cli-alpine
• 8.4-cli-alpine3.22
• 8-cli-alpine
• 8-cli-alpine3.22
• cli-alpine
• cli-alpine3.22
• alpine
• alpine3.22
• 8.4.11-alpine
• 8.4.11-alpine3.22
• 8.4-alpine3.22
• 8-alpine
• 8-alpine3.22

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 42 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.4.11

• 8.1.33-cli-alpine3.22
• 8.1-cli-alpine3.22
• 8.1.33-alpine3.22

• Patch runtime version update
• Same OS detected
• Image has similar size
• Image has same number of vulnerabilities
• Image contains similar number of packages

• Size: 36 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.1.33

• 8.4.11-cli-alpine
• 8.4.11-cli-alpine3.22
• 8.4-cli-alpine
• 8.4-cli-alpine3.22
• 8-cli-alpine
• 8-cli-alpine3.22
• cli-alpine
• cli-alpine3.22
• alpine
• alpine3.22
• 8.4.11-alpine
• 8.4.11-alpine3.22
• 8.4-alpine3.22
• 8-alpine
• 8-alpine3.22

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains similar number of packages

• Size: 42 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.4.11

• 8.4.11-cli-alpine3.21
• 8.4-cli-alpine3.21
• 8-cli-alpine3.21
• cli-alpine3.21
• alpine3.21
• 8.4.11-alpine3.21
• 8-alpine3.21

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 42 MB
• Flavor: alpine
• OS: 3.21
• Runtime: 8.4.11

• 8.3.24-cli-alpine
• 8.3.24-cli-alpine3.22
• 8.3-cli-alpine
• 8.3-cli-alpine3.22
• 8.3.24-alpine
• 8.3.24-alpine3.22
• 8.3-alpine3.22

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains similar number of packages

• Size: 37 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.3.24

• 8.3.24-cli-alpine3.21
• 8.3-cli-alpine3.21
• 8.3.24-alpine3.21

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 37 MB
• Flavor: alpine
• OS: 3.21
• Runtime: 8.3.24

• 8.2.29-cli-alpine
• 8.2.29-cli-alpine3.22
• 8.2-cli-alpine
• 8.2-cli-alpine3.22
• 8.2.29-alpine
• 8.2.29-alpine3.22
• 8.2-alpine3.22

• Same OS detected
• Minor runtime version update
• Image has similar size
• Image has same number of vulnerabilities
• Image contains similar number of packages
• 8.2-alpine was pulled 1.8K times last month

• Size: 37 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.2.29

• 8.2.29-cli-alpine3.21
• 8.2-cli-alpine3.21
• 8.2.29-alpine3.21

• Same OS detected
• Minor runtime version update
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 36 MB
• Flavor: alpine
• OS: 3.21
• Runtime: 8.2.29

• 8.3-fpm-alpine
• 8.3-fpm-alpine3.22
• 8.3.24-fpm-alpine
• 8.3.24-fpm-alpine3.22

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:golang/stdlib@1.24.3

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

• 8.4.11-cli-alpine
• 8.4.11-cli-alpine3.22
• 8.4-cli-alpine
• 8.4-cli-alpine3.22
• 8-cli-alpine
• 8-cli-alpine3.22
• cli-alpine
• cli-alpine3.22
• alpine
• alpine3.22
• 8.4.11-alpine
• 8.4.11-alpine3.22
• 8.4-alpine3.22
• 8-alpine
• 8-alpine3.22

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 42 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.4.11

• 8-alpine3.22
• 8-cli-alpine
• 8-cli-alpine3.22
• 8.4-alpine
• 8.4-alpine3.22
• 8.4-cli-alpine
• 8.4-cli-alpine3.22
• 8.4.11-alpine
• 8.4.11-alpine3.22
• 8.4.11-cli-alpine
• 8.4.11-cli-alpine3.22
• alpine
• alpine3.22
• cli-alpine
• cli-alpine3.22
• e4f9bb894d0d59558802c50d63685a084b2b4fb7eb77398e783423beab34d48f

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:golang/stdlib@1.24.3

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

• 8.4.11-fpm-alpine
• 8.4.11-fpm-alpine3.22
• 8.4-fpm-alpine3.22
• 8-fpm-alpine
• 8-fpm-alpine3.22
• fpm-alpine
• fpm-alpine3.22

• Same OS detected
• Tag was pushed more recently
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 37 MB
• Flavor: alpine
• OS: 3.22

• 8-fpm-alpine
• 8-fpm-alpine3.22
• 8.4-fpm-alpine
• 8.4-fpm-alpine3.22
• 8.4.11-fpm-alpine
• 8.4.11-fpm-alpine3.22
• fpm-alpine
• fpm-alpine3.22

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:golang/stdlib@1.24.3

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

• 8-alpine3.22
• 8-cli-alpine
• 8-cli-alpine3.22
• 8.4-alpine
• 8.4-alpine3.22
• 8.4-cli-alpine
• 8.4-cli-alpine3.22
• 8.4.11-alpine
• 8.4.11-alpine3.22
• 8.4.11-cli-alpine
• 8.4.11-cli-alpine3.22
• alpine
• alpine3.22
• cli-alpine
• cli-alpine3.22
• e4f9bb894d0d59558802c50d63685a084b2b4fb7eb77398e783423beab34d48f

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:golang/stdlib@1.24.3

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

• 8.1-fpm-alpine3.21
• 8.1.33-fpm-alpine
• 8.1.33-fpm-alpine3.21
• a5705c7e8a9637ec417dc448b6afb91982a252f2f08a056af3166d3e0b36cc0e

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH clients receiving SSH_AGENT_SUCCESS when expecting a typed response will panic and cause early termination of the client process.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:golang/stdlib@1.23.9

The ParseAddress function constructeds domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption.

The processing time for parsing some invalid inputs scales non-linearly with respect to the size of the input.

This affects programs which parse untrusted PEM inputs.

Validating certificate chains which contain DSA public keys can cause programs to panic, due to a interface cast that assumes they implement the Equal method.

This affects programs which validate arbitrary certificate chains.

Due to the design of the name constraint checking algorithm, the processing time of some inputs scals non-linearly with respect to the size of the certificate.

This affects programs which validate arbitrary certificate chains.

• 8.1.33-fpm-alpine3.22

• Patch runtime version update
• Same OS detected
• Image has similar size
• Image has same number of vulnerabilities
• Image contains similar number of packages

• Size: 32 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.1.33

• 8.3.27-fpm-alpine
• 8.3.27-fpm-alpine3.22
• 8.3-fpm-alpine3.22

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image introduces no new vulnerability but removes 5
• Image contains similar number of packages

• Size: 33 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.3.27

• 8.3.27-fpm-alpine3.21

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image introduces no new vulnerability but removes 5
• Image contains equal number of packages

• Size: 33 MB
• Flavor: alpine
• OS: 3.21
• Runtime: 8.3.27

• 8.2.29-fpm-alpine
• 8.2.29-fpm-alpine3.22
• 8.2-fpm-alpine3.22

• Same OS detected
• Minor runtime version update
• Image has similar size
• Image has same number of vulnerabilities
• Image contains similar number of packages
• 8.2-fpm-alpine was pulled 4.1K times last month

• Size: 32 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.2.29

• 8.2.29-fpm-alpine3.21

• Same OS detected
• Minor runtime version update
• Image has similar size
• Image has same number of vulnerabilities
• Image contains equal number of packages

• Size: 32 MB
• Flavor: alpine
• OS: 3.21
• Runtime: 8.2.29

• 8.4.14-fpm-alpine
• 8.4.14-fpm-alpine3.22
• 8.4-fpm-alpine3.22
• 8-fpm-alpine
• 8-fpm-alpine3.22
• fpm-alpine
• fpm-alpine3.22

• Same OS detected
• Tag was pushed more recently
• Image has similar size
• Image introduces no new vulnerability but removes 5
• Image contains similar number of packages

• Size: 36 MB
• Flavor: alpine
• OS: 3.22

• 8.4.14-fpm-alpine3.21
• 8-fpm-alpine3.21
• fpm-alpine3.21

• Same OS detected
• Tag was pushed more recently
• Image has similar size
• Image introduces no new vulnerability but removes 5
• Image contains equal number of packages

• Size: 36 MB
• Flavor: alpine
• OS: 3.21

• 8-alpine3.22
• 8-cli-alpine
• 8-cli-alpine3.22
• 8.4-alpine
• 8.4-alpine3.22
• 8.4-cli-alpine
• 8.4-cli-alpine3.22
• 8.4.14-alpine
• 8.4.14-alpine3.22
• 8.4.14-cli-alpine
• 8.4.14-cli-alpine3.22
• aea9a2da6d41c26d48544950937d654f556bffe773f82fd3924823903f67b4f5
• alpine
• alpine3.22
• cli-alpine
• cli-alpine3.22

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH clients receiving SSH_AGENT_SUCCESS when expecting a typed response will panic and cause early termination of the client process.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:golang/stdlib@1.24.8

Due to the design of the name constraint checking algorithm, the processing time of some inputs scals non-linearly with respect to the size of the certificate.

This affects programs which validate arbitrary certificate chains.

• 8.2-alpine3.22
• 8.2-cli-alpine
• 8.2-cli-alpine3.22
• 8.2.29-alpine
• 8.2.29-alpine3.22
• 8.2.29-cli-alpine
• 8.2.29-cli-alpine3.22
• df7d2aca7d453249829e16923877c821823065f32a24e0eb2c66e7a12fd7b54b

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH clients receiving SSH_AGENT_SUCCESS when expecting a typed response will panic and cause early termination of the client process.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:golang/stdlib@1.24.7

The ParseAddress function constructeds domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption.

The processing time for parsing some invalid inputs scales non-linearly with respect to the size of the input.

This affects programs which parse untrusted PEM inputs.

Validating certificate chains which contain DSA public keys can cause programs to panic, due to a interface cast that assumes they implement the Equal method.

This affects programs which validate arbitrary certificate chains.

Due to the design of the name constraint checking algorithm, the processing time of some inputs scals non-linearly with respect to the size of the certificate.

This affects programs which validate arbitrary certificate chains.

• 8-fpm-alpine
• 8-fpm-alpine3.22
• 8.4-fpm-alpine
• 8.4-fpm-alpine3.22
• 8.4.14-fpm-alpine
• 8.4.14-fpm-alpine3.22
• fpm-alpine
• fpm-alpine3.22

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH clients receiving SSH_AGENT_SUCCESS when expecting a typed response will panic and cause early termination of the client process.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:golang/stdlib@1.24.8

Due to the design of the name constraint checking algorithm, the processing time of some inputs scals non-linearly with respect to the size of the certificate.

This affects programs which validate arbitrary certificate chains.

• 8.4.14-cli-alpine
• 8.4.14-cli-alpine3.22
• 8.4-cli-alpine
• 8.4-cli-alpine3.22
• 8-cli-alpine
• 8-cli-alpine3.22
• cli-alpine
• cli-alpine3.22
• alpine
• alpine3.22
• 8.4.14-alpine
• 8.4.14-alpine3.22
• 8.4-alpine3.22
• 8-alpine
• 8-alpine3.22

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image introduces no new vulnerability but removes 5
• Image contains equal number of packages

• Size: 41 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.4.14

• 8.3.27-cli-alpine
• 8.3.27-cli-alpine3.22
• 8.3-cli-alpine
• 8.3-cli-alpine3.22
• 8.3.27-alpine
• 8.3.27-alpine3.22
• 8.3-alpine3.22

• Same OS detected
• Minor runtime version update
• Tag was pushed more recently
• Image has similar size
• Image introduces no new vulnerability but removes 5
• Image contains equal number of packages

• Size: 37 MB
• Flavor: alpine
• OS: 3.22
• Runtime: 8.3.27

• 8.1-alpine3.21
• 8.1-cli-alpine
• 8.1-cli-alpine3.21
• 8.1.33-alpine
• 8.1.33-alpine3.21
• 8.1.33-cli-alpine
• 8.1.33-cli-alpine3.21
• aeda52007687158f88915a60b395065c946a772587552d11e8e49511924585c9

pkg:golang/golang.org/x/crypto@0.17.0

Improper Authorization

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

SSH clients receiving SSH_AGENT_SUCCESS when expecting a typed response will panic and cause early termination of the client process.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

pkg:golang/stdlib@1.23.9

The ParseAddress function constructeds domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption.

The processing time for parsing some invalid inputs scales non-linearly with respect to the size of the input.

This affects programs which parse untrusted PEM inputs.

Validating certificate chains which contain DSA public keys can cause programs to panic, due to a interface cast that assumes they implement the Equal method.

This affects programs which validate arbitrary certificate chains.

Due to the design of the name constraint checking algorithm, the processing time of some inputs scals non-linearly with respect to the size of the certificate.

This affects programs which validate arbitrary certificate chains.

pkg:pypi/setuptools@70.3.0

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Summary

A path traversal vulnerability in PackageIndex was fixed in setuptools version 78.1.1

Details

    def _download_url(self, url, tmpdir):
        # Determine download filename
        #
        name, _fragment = egg_info_for_url(url)
        if name:
            while '..' in name:
                name = name.replace('..', '.').replace('\\', '_')
        else:
            name = "__downloaded__"  # default if URL has no path contents

        if name.endswith('.[egg.zip](http://egg.zip/)'):
            name = name[:-4]  # strip the extra .zip before download

 -->       filename = os.path.join(tmpdir, name)

Here: https://github.com/pypa/setuptools/blob/6ead555c5fb29bc57fe6105b1bffc163f56fd558/setuptools/package_index.py#L810C1-L825C88

os.path.join() discards the first argument tmpdir if the second begins with a slash or drive letter.
name is derived from a URL without sufficient sanitization. While there is some attempt to sanitize by replacing instances of '..' with '.', it is insufficient.

Risk Assessment

As easy_install and package_index are deprecated, the exploitation surface is reduced.
However, it seems this could be exploited in a similar fashion like GHSA-r9hx-vwmv-q579, and as described by POC 4 in GHSA-cx63-2mw6-8hw5 report: via malicious URLs present on the pages of a package index.

Impact

An attacker would be allowed to write files to arbitrary locations on the filesystem with the permissions of the process running the Python code, which could escalate to RCE depending on the context.

References

https://huntr.com/bounties/d6362117-ad57-4e83-951f-b8141c6e7ca5
pypa/setuptools#4946