-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deps(deps): update wagoid/commitlint-github-action action to v6.2.1 #80
Conversation
Outdated🔍 Vulnerabilities of
|
digest | sha256:dc593033156cd1bfdc742cbf9c964fe6913ea2bfdfe7d964040755a2bf3fe5a2 |
vulnerabilities | |
platform | linux/amd64 |
size | 109 MB |
packages | 231 |
📦 Base Image php:0f3e69aa84dedd26dfa550ca4d5dad530b2dd71fe8529ba45d7ce8585587f42e
golang.org/x/crypto
|
Affected range | <0.31.0 |
Fixed version | 0.31.0 |
CVSS Score | 9.1 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
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/[email protected] 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.
golang.org/x/net 0.18.0
(golang)
pkg:golang/golang.org/x/[email protected]
Allocation of Resources Without Limits or Throttling
Affected range | <0.33.0 |
Fixed version | 0.33.0 |
CVSS Score | 8.7 |
CVSS Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.
Outdated🔍 Vulnerabilities of
|
digest | sha256:b6c79618a664a41e2ba8dfe487aaecab49e1ca9509e338a1360d22d732107941 |
vulnerabilities | |
platform | linux/amd64 |
size | 109 MB |
packages | 232 |
📦 Base Image php:8-fpm-alpine
golang.org/x/crypto
|
Affected range | <0.31.0 |
Fixed version | 0.31.0 |
CVSS Score | 9.1 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
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/[email protected] 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.
golang.org/x/net 0.18.0
(golang)
pkg:golang/golang.org/x/[email protected]
Allocation of Resources Without Limits or Throttling
Affected range | <0.33.0 |
Fixed version | 0.33.0 |
CVSS Score | 8.7 |
CVSS Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.
Outdated🔍 Vulnerabilities of
|
digest | sha256:24cca42b76a38a8779ae4b81a3916fb62cb1df47c147736b3df7af985a9d5b6f |
vulnerabilities | |
platform | linux/amd64 |
size | 127 MB |
packages | 249 |
📦 Base Image php:0f3e69aa84dedd26dfa550ca4d5dad530b2dd71fe8529ba45d7ce8585587f42e
also known as |
|
digest | sha256:39bf59caddad3b212fdd32aff3462885ccdc18e754a9e392e543b4a35effec7c |
vulnerabilities |
golang.org/x/crypto
|
Affected range | <0.31.0 |
Fixed version | 0.31.0 |
CVSS Score | 9.1 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
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/[email protected] 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.
golang.org/x/net 0.18.0
(golang)
pkg:golang/golang.org/x/[email protected]
Allocation of Resources Without Limits or Throttling
Affected range | <0.33.0 |
Fixed version | 0.33.0 |
CVSS Score | 8.7 |
CVSS Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.
OutdatedRecommended fixes for image
|
Name | fpm-alpine3.21 |
Digest | sha256:bc96c09ec08672e2c2f3b548d388a99089231bc7b50c0284e378741300807110 |
Vulnerabilities | |
Pushed | 3 weeks ago |
Size | 36 MB |
Packages | 53 |
Flavor | alpine |
OS | 3.21 |
The base image is also available under the supported tag(s):8-fpm-alpine3.21
,8.4-fpm-alpine
,8.4-fpm-alpine3.21
,8.4.2-fpm-alpine
,8.4.2-fpm-alpine3.21
,fpm-alpine
,fpm-alpine3.21
Refresh base image
Rebuild the image using a newer base image version. Updating this may result in breaking changes.✅ This image version is up to date.
Change base image
Tag | Details | Pushed | Vulnerabilities |
---|---|---|---|
8.3-fpm-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
8.2-fpm-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
8.1-fpm-alpine Minor runtime version update Also known as:
|
Benefits:
|
1 month ago | |
Outdated🔍 Vulnerabilities of
|
digest | sha256:69bdebc0c0c837e8caf7ea62576ff7c97a843751cabb9ba9940d999044856c86 |
vulnerabilities | |
platform | linux/amd64 |
size | 126 MB |
packages | 249 |
📦 Base Image php:2b53de2fdc87e38f450a4c42f995704c4bc3bc789f010d1a69a860538f12fe60
also known as |
|
digest | sha256:8ed48e85630b00d7dde300f7c205e502495d8a117a254924bf07f4dcac3df52f |
vulnerabilities |
golang.org/x/crypto
|
Affected range | <0.31.0 |
Fixed version | 0.31.0 |
CVSS Score | 9.1 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
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/[email protected] 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.
golang.org/x/net 0.18.0
(golang)
pkg:golang/golang.org/x/[email protected]
Allocation of Resources Without Limits or Throttling
Affected range | <0.33.0 |
Fixed version | 0.33.0 |
CVSS Score | 8.7 |
CVSS Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.
Outdated🔍 Vulnerabilities of
|
digest | sha256:dd814c02c5053860a3577cb49b8864912faa9d07196381ab10b37f83ec978994 |
vulnerabilities | |
platform | linux/amd64 |
size | 105 MB |
packages | 232 |
📦 Base Image php:8.3-fpm-alpine
also known as |
|
digest | sha256:60f5489bacbe41914142ab673d6727c8516bc61e6da16fbf0f40f67b33c8f5ac |
vulnerabilities |
golang.org/x/crypto
|
Affected range | <0.31.0 |
Fixed version | 0.31.0 |
CVSS Score | 9.1 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
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/[email protected] 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.
golang.org/x/net 0.18.0
(golang)
pkg:golang/golang.org/x/[email protected]
Allocation of Resources Without Limits or Throttling
Affected range | <0.33.0 |
Fixed version | 0.33.0 |
CVSS Score | 8.7 |
CVSS Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.
OutdatedRecommended fixes for image
|
Name | 8.1.31-alpine3.21 |
Digest | sha256:8ed48e85630b00d7dde300f7c205e502495d8a117a254924bf07f4dcac3df52f |
Vulnerabilities | |
Pushed | 1 month ago |
Size | 36 MB |
Packages | 52 |
Flavor | alpine |
OS | 3.21 |
Runtime | 8.1.31 |
The base image is also available under the supported tag(s):8.1-alpine3.21
,8.1-cli-alpine
,8.1-cli-alpine3.21
,8.1.31-alpine
,8.1.31-alpine3.21
,8.1.31-cli-alpine
,8.1.31-cli-alpine3.21
Refresh base image
Rebuild the image using a newer base image version. Updating this may result in breaking changes.✅ This image version is up to date.
Change base image
Tag | Details | Pushed | Vulnerabilities |
---|---|---|---|
8.4-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
8.3-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
8.2-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
OutdatedRecommended fixes for image
|
Name | 8.2.27-alpine3.21 |
Digest | sha256:39bf59caddad3b212fdd32aff3462885ccdc18e754a9e392e543b4a35effec7c |
Vulnerabilities | |
Pushed | 3 weeks ago |
Size | 36 MB |
Packages | 52 |
Flavor | alpine |
OS | 3.21 |
Runtime | 8.2.27 |
The base image is also available under the supported tag(s):8.2-alpine3.21
,8.2-cli-alpine
,8.2-cli-alpine3.21
,8.2.27-alpine
,8.2.27-alpine3.21
,8.2.27-cli-alpine
,8.2.27-cli-alpine3.21
Refresh base image
Rebuild the image using a newer base image version. Updating this may result in breaking changes.✅ This image version is up to date.
Change base image
Tag | Details | Pushed | Vulnerabilities |
---|---|---|---|
8.4-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
8.3-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
OutdatedRecommended fixes for image
|
Name | 8.3.15-fpm-alpine3.21 |
Digest | sha256:60f5489bacbe41914142ab673d6727c8516bc61e6da16fbf0f40f67b33c8f5ac |
Vulnerabilities | |
Pushed | 3 weeks ago |
Size | 33 MB |
Packages | 53 |
Flavor | alpine |
OS | 3.21 |
Runtime | 8.3.15 |
The base image is also available under the supported tag(s):8.3-fpm-alpine3.21
,8.3.15-fpm-alpine
,8.3.15-fpm-alpine3.21
Refresh base image
Rebuild the image using a newer base image version. Updating this may result in breaking changes.✅ This image version is up to date.
Change base image
Tag | Details | Pushed | Vulnerabilities |
---|---|---|---|
8.4-fpm-alpine Image has same number of vulnerabilities Also known as:
|
Benefits:
|
3 weeks ago | |
Outdated🔍 Vulnerabilities of
|
digest | sha256:2064ecabed7f82f968baa0f2e70bed8e805a1d656440bf2e80f7094ad1d7a087 |
vulnerabilities | |
platform | linux/amd64 |
size | 104 MB |
packages | 232 |
📦 Base Image php:8.2-fpm-alpine
also known as |
|
digest | sha256:76f65a70210d2d9ff8f8e61305049bf0973d00a91a96f9440c8b5b47ee2e93f5 |
vulnerabilities |
golang.org/x/crypto
|
Affected range | <0.31.0 |
Fixed version | 0.31.0 |
CVSS Score | 9.1 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
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/[email protected] 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.
golang.org/x/net 0.18.0
(golang)
pkg:golang/golang.org/x/[email protected]
Allocation of Resources Without Limits or Throttling
Affected range | <0.33.0 |
Fixed version | 0.33.0 |
CVSS Score | 8.7 |
CVSS Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.
Outdated🔍 Vulnerabilities of
|
digest | sha256:7e05a42bff07b15e46fe7da3f62179cec2381c027a43d56b09e93b42f3b6abc3 |
vulnerabilities | |
platform | linux/amd64 |
size | 110 MB |
packages | 231 |
📦 Base Image php:6e49486e9968f51322ecc06a80b5bbf7f1e01c3b21721a3e1fb80e4ab5f5644d
also known as |
|
digest | sha256:736d8855dd8bcadc28dde75a9af8c7165c3038cd154b61f6cd1aa49c7691fad2 |
vulnerabilities |
golang.org/x/crypto
|
Affected range | <0.31.0 |
Fixed version | 0.31.0 |
CVSS Score | 9.1 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
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/[email protected] 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.
golang.org/x/net 0.18.0
(golang)
pkg:golang/golang.org/x/[email protected]
Allocation of Resources Without Limits or Throttling
Affected range | <0.33.0 |
Fixed version | 0.33.0 |
CVSS Score | 8.7 |
CVSS Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.
Outdated🔍 Vulnerabilities of
|
digest | sha256:eafb46de71f29057ba49c259d3dfcaaa99a0e17c1103065449bb93b8c2481e2b |
vulnerabilities | |
platform | linux/amd64 |
size | 128 MB |
packages | 249 |
📦 Base Image php:6e49486e9968f51322ecc06a80b5bbf7f1e01c3b21721a3e1fb80e4ab5f5644d
also known as |
|
digest | sha256:736d8855dd8bcadc28dde75a9af8c7165c3038cd154b61f6cd1aa49c7691fad2 |
vulnerabilities |
golang.org/x/crypto
|
Affected range | <0.31.0 |
Fixed version | 0.31.0 |
CVSS Score | 9.1 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
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/[email protected] 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.
golang.org/x/net 0.18.0
(golang)
pkg:golang/golang.org/x/[email protected]
Allocation of Resources Without Limits or Throttling
Affected range | <0.33.0 |
Fixed version | 0.33.0 |
CVSS Score | 8.7 |
CVSS Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.
OutdatedRecommended fixes for image
|
Name | 8.2.27-fpm-alpine3.21 |
Digest | sha256:76f65a70210d2d9ff8f8e61305049bf0973d00a91a96f9440c8b5b47ee2e93f5 |
Vulnerabilities | |
Pushed | 3 weeks ago |
Size | 32 MB |
Packages | 53 |
Flavor | alpine |
OS | 3.21 |
Runtime | 8.2.27 |
The base image is also available under the supported tag(s):8.2-fpm-alpine3.21
,8.2.27-fpm-alpine
,8.2.27-fpm-alpine3.21
Refresh base image
Rebuild the image using a newer base image version. Updating this may result in breaking changes.✅ This image version is up to date.
Change base image
Tag | Details | Pushed | Vulnerabilities |
---|---|---|---|
8.3-fpm-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
8.4-fpm-alpine Image has same number of vulnerabilities Also known as:
|
Benefits:
|
3 weeks ago | |
Outdated🔍 Vulnerabilities of
|
digest | sha256:72fd100a64721b0aa9acf9b49453b15b229176ae4df83f08ca05c032db4cad90 |
vulnerabilities | |
platform | linux/amd64 |
size | 115 MB |
packages | 231 |
📦 Base Image php:6ef85564cb5069d1c254b4525a0cedc7e669a9f9c02539b0d8056b68b827870a
also known as |
|
digest | sha256:6d15520dc9f2178430ff79f52b914de9dd7a31bf87de2fe464fc4953a4568211 |
vulnerabilities |
golang.org/x/crypto
|
Affected range | <0.31.0 |
Fixed version | 0.31.0 |
CVSS Score | 9.1 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
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/[email protected] 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.
golang.org/x/net 0.18.0
(golang)
pkg:golang/golang.org/x/[email protected]
Allocation of Resources Without Limits or Throttling
Affected range | <0.33.0 |
Fixed version | 0.33.0 |
CVSS Score | 8.7 |
CVSS Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.
OutdatedRecommended fixes for image
|
Name | 8.3.15-alpine3.21 |
Digest | sha256:736d8855dd8bcadc28dde75a9af8c7165c3038cd154b61f6cd1aa49c7691fad2 |
Vulnerabilities | |
Pushed | 3 weeks ago |
Size | 37 MB |
Packages | 52 |
Flavor | alpine |
OS | 3.21 |
Runtime | 8.3.15 |
The base image is also available under the supported tag(s):8.3-alpine3.21
,8.3-cli-alpine
,8.3-cli-alpine3.21
,8.3.15-alpine
,8.3.15-alpine3.21
,8.3.15-cli-alpine
,8.3.15-cli-alpine3.21
Refresh base image
Rebuild the image using a newer base image version. Updating this may result in breaking changes.✅ This image version is up to date.
Change base image
Tag | Details | Pushed | Vulnerabilities |
---|---|---|---|
8.4-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
1 similar comment
OutdatedRecommended fixes for image
|
Name | 8.3.15-alpine3.21 |
Digest | sha256:736d8855dd8bcadc28dde75a9af8c7165c3038cd154b61f6cd1aa49c7691fad2 |
Vulnerabilities | |
Pushed | 3 weeks ago |
Size | 37 MB |
Packages | 52 |
Flavor | alpine |
OS | 3.21 |
Runtime | 8.3.15 |
The base image is also available under the supported tag(s):8.3-alpine3.21
,8.3-cli-alpine
,8.3-cli-alpine3.21
,8.3.15-alpine
,8.3.15-alpine3.21
,8.3.15-cli-alpine
,8.3.15-cli-alpine3.21
Refresh base image
Rebuild the image using a newer base image version. Updating this may result in breaking changes.✅ This image version is up to date.
Change base image
Tag | Details | Pushed | Vulnerabilities |
---|---|---|---|
8.4-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
OutdatedRecommended fixes for image
|
Name | 8.4.2-alpine3.21 |
Digest | sha256:6d15520dc9f2178430ff79f52b914de9dd7a31bf87de2fe464fc4953a4568211 |
Vulnerabilities | |
Pushed | 3 weeks ago |
Size | 42 MB |
Packages | 52 |
Flavor | alpine |
OS | 3.21 |
Runtime | 8.4.2 |
The base image is also available under the supported tag(s):8-alpine3.21
,8-cli-alpine
,8-cli-alpine3.21
,8.4-alpine
,8.4-alpine3.21
,8.4-cli-alpine
,8.4-cli-alpine3.21
,8.4.2-alpine
,8.4.2-alpine3.21
,8.4.2-cli-alpine
,8.4.2-cli-alpine3.21
,alpine
,alpine3.21
,cli-alpine
,cli-alpine3.21
Refresh base image
Rebuild the image using a newer base image version. Updating this may result in breaking changes.✅ This image version is up to date.
Change base image
✅ There are no tag recommendations at this time.
Outdated🔍 Vulnerabilities of
|
digest | sha256:b3e3908fd32c1618c1ec3e9075d041585d693c08c93a591b07008f6ccf94d9f1 |
vulnerabilities | |
platform | linux/amd64 |
size | 133 MB |
packages | 249 |
📦 Base Image php:6ef85564cb5069d1c254b4525a0cedc7e669a9f9c02539b0d8056b68b827870a
also known as |
|
digest | sha256:6d15520dc9f2178430ff79f52b914de9dd7a31bf87de2fe464fc4953a4568211 |
vulnerabilities |
golang.org/x/crypto
|
Affected range | <0.31.0 |
Fixed version | 0.31.0 |
CVSS Score | 9.1 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
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/[email protected] 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.
golang.org/x/net 0.18.0
(golang)
pkg:golang/golang.org/x/[email protected]
Allocation of Resources Without Limits or Throttling
Affected range | <0.33.0 |
Fixed version | 0.33.0 |
CVSS Score | 8.7 |
CVSS Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.
OutdatedRecommended fixes for image
|
Name | 8.4.2-alpine3.21 |
Digest | sha256:6d15520dc9f2178430ff79f52b914de9dd7a31bf87de2fe464fc4953a4568211 |
Vulnerabilities | |
Pushed | 3 weeks ago |
Size | 42 MB |
Packages | 52 |
Flavor | alpine |
OS | 3.21 |
Runtime | 8.4.2 |
The base image is also available under the supported tag(s):8-alpine3.21
,8-cli-alpine
,8-cli-alpine3.21
,8.4-alpine
,8.4-alpine3.21
,8.4-cli-alpine
,8.4-cli-alpine3.21
,8.4.2-alpine
,8.4.2-alpine3.21
,8.4.2-cli-alpine
,8.4.2-cli-alpine3.21
,alpine
,alpine3.21
,cli-alpine
,cli-alpine3.21
Refresh base image
Rebuild the image using a newer base image version. Updating this may result in breaking changes.✅ This image version is up to date.
Change base image
✅ There are no tag recommendations at this time.
🔍 Vulnerabilities of
|
digest | sha256:f969e6b6320ee0cb879c877fd9deebc454ca123f46a0f935a963a3749a89dcaf |
vulnerabilities | |
platform | linux/amd64 |
size | 108 MB |
packages | 231 |
📦 Base Image php:2b53de2fdc87e38f450a4c42f995704c4bc3bc789f010d1a69a860538f12fe60
also known as |
|
digest | sha256:8ed48e85630b00d7dde300f7c205e502495d8a117a254924bf07f4dcac3df52f |
vulnerabilities |
golang.org/x/crypto
|
Affected range | <0.31.0 |
Fixed version | 0.31.0 |
CVSS Score | 9.1 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
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/[email protected] 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.
golang.org/x/net 0.18.0
(golang)
pkg:golang/golang.org/x/[email protected]
Allocation of Resources Without Limits or Throttling
Affected range | <0.33.0 |
Fixed version | 0.33.0 |
CVSS Score | 8.7 |
CVSS Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.
🔍 Vulnerabilities of
|
digest | sha256:cd7674c056490cdaedc7f640b17ed009ab8c05abc6ad503316b33621f51f70f5 |
vulnerabilities | |
platform | linux/amd64 |
size | 104 MB |
packages | 232 |
📦 Base Image php:54b5ff554357a1100058bcce13b21851a693ca1636d4d8dae493079075d47ba0
also known as |
|
digest | sha256:845dccbc2cf56631ba4f1d800eeb7d6a797efdae00a5e1c78b898cd67db26f48 |
vulnerabilities |
golang.org/x/crypto
|
Affected range | <0.31.0 |
Fixed version | 0.31.0 |
CVSS Score | 9.1 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
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/[email protected] 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.
golang.org/x/net 0.18.0
(golang)
pkg:golang/golang.org/x/[email protected]
Allocation of Resources Without Limits or Throttling
Affected range | <0.33.0 |
Fixed version | 0.33.0 |
CVSS Score | 8.7 |
CVSS Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
EPSS Score | 0.045% |
EPSS Percentile | 18th percentile |
Description
An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.
Recommended fixes for image
|
Name | 8.1.31-alpine3.21 |
Digest | sha256:8ed48e85630b00d7dde300f7c205e502495d8a117a254924bf07f4dcac3df52f |
Vulnerabilities | |
Pushed | 1 month ago |
Size | 36 MB |
Packages | 52 |
Flavor | alpine |
OS | 3.21 |
Runtime | 8.1.31 |
The base image is also available under the supported tag(s):8.1-alpine3.21
,8.1-cli-alpine
,8.1-cli-alpine3.21
,8.1.31-alpine
,8.1.31-alpine3.21
,8.1.31-cli-alpine
,8.1.31-cli-alpine3.21
Refresh base image
Rebuild the image using a newer base image version. Updating this may result in breaking changes.✅ This image version is up to date.
Change base image
Tag | Details | Pushed | Vulnerabilities |
---|---|---|---|
8.4-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
8.3-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
8.2-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
Recommended fixes for image
|
Name | 8.1.31-fpm-alpine3.21 |
Digest | sha256:845dccbc2cf56631ba4f1d800eeb7d6a797efdae00a5e1c78b898cd67db26f48 |
Vulnerabilities | |
Pushed | 1 month ago |
Size | 32 MB |
Packages | 53 |
Flavor | alpine |
OS | 3.21 |
Runtime | 8.1.31 |
The base image is also available under the supported tag(s):8.1-fpm-alpine3.21
,8.1.31-fpm-alpine
,8.1.31-fpm-alpine3.21
Refresh base image
Rebuild the image using a newer base image version. Updating this may result in breaking changes.✅ This image version is up to date.
Change base image
Tag | Details | Pushed | Vulnerabilities |
---|---|---|---|
8.3-fpm-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
8.2-fpm-alpine Minor runtime version update Also known as:
|
Benefits:
|
3 weeks ago | |
8.4-fpm-alpine Image has same number of vulnerabilities Also known as:
|
Benefits:
|
3 weeks ago | |
This PR contains the following updates:
v6.2.0
->v6.2.1
Release Notes
wagoid/commitlint-github-action (wagoid/commitlint-github-action)
v6.2.1
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.