Skip to content

deps(deps): update actions/download-artifact action to v5 #111

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 6, 2025

This PR contains the following updates:

Package Type Update Change
actions/download-artifact action major v4 -> v5

Release Notes

actions/download-artifact (actions/download-artifact)

v5

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from lotyp as a code owner August 6, 2025 01:42
@renovate renovate bot enabled auto-merge (squash) August 6, 2025 01:42
@github-actions github-actions bot added the type: maintenance For maintenance, refactor and testing (perf, chore, style, revert, refactor, test, build, ci) label Aug 6, 2025
Copy link

github-actions bot commented Aug 6, 2025

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:72b7dfa62ae0d07a69ff1d58aa983104f0c33897033d38c17ff051c98b8f9512
vulnerabilitiescritical: 1 high: 1 medium: 0 low: 0
platformlinux/amd64
size109 MB
packages247
📦 Base Image php:8.1-alpine
also known as
  • 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
digestsha256:6ed5103426b2c742dcc4721afa9864e7faaedcbb84c92410762d0c5162a8bdb2
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

pkg:golang/golang.org/x/[email protected]

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th 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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

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.

Copy link

github-actions bot commented Aug 6, 2025

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:b763079158741fef7590119484b50f9f5611eb6dc585b41240fd880f9a08f5f9
vulnerabilitiescritical: 1 high: 2 medium: 0 low: 0
platformlinux/amd64
size108 MB
packages250
📦 Base Image php:2bc2a355c610a5ce2f4854d785c740aafe346f652caa7a4960796338a17a0ffe
also known as
  • 8.3-fpm-alpine
  • 8.3-fpm-alpine3.22
  • 8.3.24-fpm-alpine
  • 8.3.24-fpm-alpine3.22
digestsha256:994a36314a28fed17d2d9d66ff694817dcf51343c7d42e1890ec75b3406a3caf
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

pkg:golang/golang.org/x/[email protected]

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th 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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

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.

critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/[email protected]

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

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.

Copy link

github-actions bot commented Aug 6, 2025

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:4cdedf1109da796ce7d8d2b1e9bbb1a22d91e5841e2d7eba836c2824552776b4
vulnerabilitiescritical: 1 high: 2 medium: 0 low: 0
platformlinux/amd64
size131 MB
packages284
📦 Base Image php:8.2-alpine
also known as
  • 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
digestsha256:cdee2ae021443a0806843448eb174a188d6e6d85377a2e5a9bcd44161001fb8d
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

pkg:golang/golang.org/x/[email protected]

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th 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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

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.

critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/[email protected]

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

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.

Copy link

github-actions bot commented Aug 6, 2025

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.1-alpine

Name8.1.33-alpine3.21
Digestsha256:6ed5103426b2c742dcc4721afa9864e7faaedcbb84c92410762d0c5162a8bdb2
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed5 days ago
Size36 MB
Packages59
Flavoralpine
OS3.21
Runtime8.1.33
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.33-alpine, 8.1.33-alpine3.21, 8.1.33-cli-alpine, 8.1.33-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

TagDetailsPushedVulnerabilities
8.1-alpine3.22
Patch runtime version update
Also known as:
  • 8.1.33-cli-alpine3.22
  • 8.1-cli-alpine3.22
  • 8.1.33-alpine3.22
Benefits:
  • Patch runtime version update
  • Same OS detected
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains similar number of packages
Image details:
  • Size: 36 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.1.33
5 days ago



8.4-alpine
Minor runtime version update
Also known as:
  • 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
Benefits:
  • 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
Image details:
  • Size: 42 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.11
5 days ago



8.4-alpine3.21
Minor runtime version update
Also known as:
  • 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
Benefits:
  • 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
Image details:
  • Size: 42 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.4.11
5 days ago



8.3-alpine
Minor runtime version update
Also known as:
  • 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
Benefits:
  • 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
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.3.24
5 days ago



8.3-alpine3.21
Minor runtime version update
Also known as:
  • 8.3.24-cli-alpine3.21
  • 8.3-cli-alpine3.21
  • 8.3.24-alpine3.21
Benefits:
  • 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
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.3.24
5 days ago



8.2-alpine
Minor runtime version update
Also known as:
  • 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
Benefits:
  • 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
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.2.29
5 days ago



8.2-alpine3.21
Minor runtime version update
Also known as:
  • 8.2.29-cli-alpine3.21
  • 8.2-cli-alpine3.21
  • 8.2.29-alpine3.21
Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 36 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.2.29
5 days ago



Copy link

github-actions bot commented Aug 6, 2025

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.3-fpm-alpine

Name8.3.24-fpm-alpine3.22
Digestsha256:994a36314a28fed17d2d9d66ff694817dcf51343c7d42e1890ec75b3406a3caf
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed5 days ago
Size33 MB
Packages61
Flavoralpine
OS3.22
Runtime8.3.24
The base image is also available under the supported tag(s): 8.3-fpm-alpine3.22, 8.3.24-fpm-alpine, 8.3.24-fpm-alpine3.22

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

TagDetailsPushedVulnerabilities
8.4-fpm-alpine
Image has same number of vulnerabilities
Also known as:
  • 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
Benefits:
  • Same OS detected
  • Tag was pushed more recently
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
5 days ago



Copy link

github-actions bot commented Aug 6, 2025

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.2-alpine

Name8.2.29-alpine3.22
Digestsha256:cdee2ae021443a0806843448eb174a188d6e6d85377a2e5a9bcd44161001fb8d
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed5 days ago
Size37 MB
Packages60
Flavoralpine
OS3.22
Runtime8.2.29
The base image is also available under the supported tag(s): 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

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

TagDetailsPushedVulnerabilities
8.4-alpine
Minor runtime version update
Also known as:
  • 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
Benefits:
  • 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
Image details:
  • Size: 42 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.11
5 days ago



8.3-alpine
Minor runtime version update
Also known as:
  • 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
Benefits:
  • 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
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.3.24
5 days ago



Copy link

github-actions bot commented Aug 6, 2025

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:c26356f10d91294f1623e4fc0d9bed1968405bb2b5d6a4847d8cbfbd2de68044
vulnerabilitiescritical: 1 high: 1 medium: 0 low: 0
platformlinux/amd64
size104 MB
packages248
📦 Base Image php:8.1-fpm-alpine
also known as
  • 8.1-fpm-alpine3.21
  • 8.1.33-fpm-alpine
  • 8.1.33-fpm-alpine3.21
  • da3eabe89d0c6c833838e3480d063d65f38577bc37dc976948b9352f3fb3d2fb
digestsha256:4268ab6c629f48d1f77ff76b70355c1f384d95028c301d7a9d07a5f1644d4072
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

pkg:golang/golang.org/x/[email protected]

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th 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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

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.

Copy link

github-actions bot commented Aug 6, 2025

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:c4d75c09ad7943481a4ab4c2f67db0a1b521c430ea785803b1c1b3b41d108644
vulnerabilitiescritical: 1 high: 2 medium: 0 low: 0
platformlinux/amd64
size132 MB
packages284
📦 Base Image php:8.3-alpine
also known as
  • 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
digestsha256:f43a903b3e7fb97ce6ecdc8ab54c4beeebc913c38697740c6e9dd0d69fc37322
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

pkg:golang/golang.org/x/[email protected]

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th 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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

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.

critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/[email protected]

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

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.

Copy link

github-actions bot commented Aug 6, 2025

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:b555d8c6ce34bb55ea5cf7a400277d3592f64ec23ebd0f0bda82a303fede23d5
vulnerabilitiescritical: 1 high: 2 medium: 0 low: 0
platformlinux/amd64
size127 MB
packages265
📦 Base Image php:8.1-alpine
also known as
  • 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
digestsha256:6ed5103426b2c742dcc4721afa9864e7faaedcbb84c92410762d0c5162a8bdb2
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

pkg:golang/golang.org/x/[email protected]

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th 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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

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.

critical: 0 high: 1 medium: 0 low: 0 setuptools 70.3.0 (pypi)

pkg:pypi/[email protected]

high 7.7: CVE--2025--47273 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Affected range<78.1.1
Fixed version78.1.1
CVSS Score7.7
CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P
EPSS Score0.139%
EPSS Percentile35th percentile
Description

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

Copy link

github-actions bot commented Aug 6, 2025

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:2598ccec405242b4ed03e6c393d04b7d0d29cdeac5028a2351e16c6131158cec
vulnerabilitiescritical: 1 high: 2 medium: 0 low: 0
platformlinux/amd64
size108 MB
packages250
📦 Base Image php:3effc26a4a8524994f6fd9e3c99f564bfdee610687d2d1d455996608118a910f
also known as
  • 8.2-fpm-alpine
  • 8.2-fpm-alpine3.22
  • 8.2.29-fpm-alpine
  • 8.2.29-fpm-alpine3.22
digestsha256:a992b4453c7ffe21584867dced3a8b82c896603a10bfe3f7ec734729e26fcda5
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

pkg:golang/golang.org/x/[email protected]

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th 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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

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.

critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/[email protected]

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

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.

Copy link

github-actions bot commented Aug 6, 2025

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.2-fpm-alpine

Name8.2.29-fpm-alpine3.22
Digestsha256:a992b4453c7ffe21584867dced3a8b82c896603a10bfe3f7ec734729e26fcda5
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed5 days ago
Size32 MB
Packages61
Flavoralpine
OS3.22
Runtime8.2.29
The base image is also available under the supported tag(s): 8.2-fpm-alpine3.22, 8.2.29-fpm-alpine, 8.2.29-fpm-alpine3.22

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

TagDetailsPushedVulnerabilities
8.3-fpm-alpine
Minor runtime version update
Also known as:
  • 8.3.24-fpm-alpine
  • 8.3.24-fpm-alpine3.22
  • 8.3-fpm-alpine3.22
Benefits:
  • 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
Image details:
  • Size: 33 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.3.24
5 days ago



8.4-fpm-alpine
Image has same number of vulnerabilities
Also known as:
  • 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
Benefits:
  • Same OS detected
  • Tag was pushed more recently
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
5 days ago



Copy link

github-actions bot commented Aug 6, 2025

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.1-fpm-alpine

Name8.1.33-fpm-alpine3.21
Digestsha256:4268ab6c629f48d1f77ff76b70355c1f384d95028c301d7a9d07a5f1644d4072
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed5 days ago
Size32 MB
Packages60
Flavoralpine
OS3.21
Runtime8.1.33
The base image is also available under the supported tag(s): 8.1-fpm-alpine3.21, 8.1.33-fpm-alpine, 8.1.33-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

TagDetailsPushedVulnerabilities
8.1-fpm-alpine3.22
Patch runtime version update
Also known as:
  • 8.1.33-fpm-alpine3.22
Benefits:
  • Patch runtime version update
  • Same OS detected
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains similar number of packages
Image details:
  • Size: 32 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.1.33
5 days ago



8.3-fpm-alpine
Minor runtime version update
Also known as:
  • 8.3.24-fpm-alpine
  • 8.3.24-fpm-alpine3.22
  • 8.3-fpm-alpine3.22
Benefits:
  • 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
Image details:
  • Size: 33 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.3.24
5 days ago



8.3-fpm-alpine3.21
Minor runtime version update
Also known as:
  • 8.3.24-fpm-alpine3.21
Benefits:
  • 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
Image details:
  • Size: 33 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.3.24
5 days ago



8.2-fpm-alpine
Minor runtime version update
Also known as:
  • 8.2.29-fpm-alpine
  • 8.2.29-fpm-alpine3.22
  • 8.2-fpm-alpine3.22
Benefits:
  • 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
Image details:
  • Size: 32 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.2.29
5 days ago



8.2-fpm-alpine3.21
Minor runtime version update
Also known as:
  • 8.2.29-fpm-alpine3.21
Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 32 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.2.29
5 days ago



8.4-fpm-alpine
Image has same number of vulnerabilities
Also known as:
  • 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
Benefits:
  • Same OS detected
  • Tag was pushed more recently
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains similar number of packages
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
5 days ago



8.4-fpm-alpine3.21
Image has same number of vulnerabilities
Also known as:
  • 8.4.11-fpm-alpine3.21
  • 8-fpm-alpine3.21
  • fpm-alpine3.21
Benefits:
  • Same OS detected
  • Tag was pushed more recently
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 36 MB
  • Flavor: alpine
  • OS: 3.21
5 days ago



Copy link

github-actions bot commented Aug 6, 2025

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.1-alpine

Name8.1.33-alpine3.21
Digestsha256:6ed5103426b2c742dcc4721afa9864e7faaedcbb84c92410762d0c5162a8bdb2
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed5 days ago
Size36 MB
Packages59
Flavoralpine
OS3.21
Runtime8.1.33
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.33-alpine, 8.1.33-alpine3.21, 8.1.33-cli-alpine, 8.1.33-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

TagDetailsPushedVulnerabilities
8.1-alpine3.22
Patch runtime version update
Also known as:
  • 8.1.33-cli-alpine3.22
  • 8.1-cli-alpine3.22
  • 8.1.33-alpine3.22
Benefits:
  • Patch runtime version update
  • Same OS detected
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains similar number of packages
Image details:
  • Size: 36 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.1.33
5 days ago



8.4-alpine
Minor runtime version update
Also known as:
  • 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
Benefits:
  • 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
Image details:
  • Size: 42 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.11
5 days ago



8.4-alpine3.21
Minor runtime version update
Also known as:
  • 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
Benefits:
  • 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
Image details:
  • Size: 42 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.4.11
5 days ago



8.3-alpine
Minor runtime version update
Also known as:
  • 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
Benefits:
  • 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
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.3.24
5 days ago



8.3-alpine3.21
Minor runtime version update
Also known as:
  • 8.3.24-cli-alpine3.21
  • 8.3-cli-alpine3.21
  • 8.3.24-alpine3.21
Benefits:
  • 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
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.3.24
5 days ago



8.2-alpine
Minor runtime version update
Also known as:
  • 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
Benefits:
  • 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
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.2.29
5 days ago



8.2-alpine3.21
Minor runtime version update
Also known as:
  • 8.2.29-cli-alpine3.21
  • 8.2-cli-alpine3.21
  • 8.2.29-alpine3.21
Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 36 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.2.29
5 days ago



Copy link

github-actions bot commented Aug 6, 2025

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.3-alpine

Name8.3.24-alpine3.22
Digestsha256:f43a903b3e7fb97ce6ecdc8ab54c4beeebc913c38697740c6e9dd0d69fc37322
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed5 days ago
Size37 MB
Packages60
Flavoralpine
OS3.22
Runtime8.3.24
The base image is also available under the supported tag(s): 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

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

TagDetailsPushedVulnerabilities
8.4-alpine
Minor runtime version update
Also known as:
  • 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
Benefits:
  • 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
Image details:
  • Size: 42 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.11
5 days ago



Copy link

github-actions bot commented Aug 6, 2025

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:d39c905ebf9ffd8d3bf485d98a4a67d502b5618653aa5c91a0a8b2a9c41d9f37
vulnerabilitiescritical: 1 high: 2 medium: 0 low: 0
platformlinux/amd64
size112 MB
packages250
📦 Base Image php:639b54f0afafe1a50d5dfdf4306b05aa09357ed7292390e3ed242ecfc57cc7e0
also known as
  • 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
digestsha256:dd4b38d02d63413f45aea06eaaf1ac2410b7cbe81b017efd3d6feefb142809b2
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

pkg:golang/golang.org/x/[email protected]

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th 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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

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.

critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/[email protected]

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

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.

Copy link

github-actions bot commented Aug 6, 2025

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8-fpm-alpine

Namefpm-alpine3.22
Digestsha256:dd4b38d02d63413f45aea06eaaf1ac2410b7cbe81b017efd3d6feefb142809b2
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed5 days ago
Size37 MB
Packages61
Flavoralpine
OS3.22
The base image is also available under the supported tag(s): 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

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

TagDetailsPushedVulnerabilities
8.3-fpm-alpine
Minor runtime version update
Also known as:
  • 8.3.24-fpm-alpine
  • 8.3.24-fpm-alpine3.22
  • 8.3-fpm-alpine3.22
Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 3.3 MB
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 33 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.3.24
5 days ago



8.2-fpm-alpine
Minor runtime version update
Also known as:
  • 8.2.29-fpm-alpine
  • 8.2.29-fpm-alpine3.22
  • 8.2-fpm-alpine3.22
Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 4.0 MB
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
  • 8.2-fpm-alpine was pulled 4.1K times last month
Image details:
  • Size: 32 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.2.29
5 days ago



8.1-fpm-alpine3.22
Minor runtime version update
Also known as:
  • 8.1.33-fpm-alpine3.22
Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 4.5 MB
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 32 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.1.33
5 days ago



Copy link

github-actions bot commented Aug 6, 2025

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:4673c81118537722678f18a07ded7f184fbb520b527f1295762627e210f7a386
vulnerabilitiescritical: 1 high: 2 medium: 0 low: 0
platformlinux/amd64
size112 MB
packages249
📦 Base Image php:8.2-alpine
also known as
  • 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
digestsha256:cdee2ae021443a0806843448eb174a188d6e6d85377a2e5a9bcd44161001fb8d
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

pkg:golang/golang.org/x/[email protected]

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th 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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

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.

critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/[email protected]

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

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.

Copy link

github-actions bot commented Aug 6, 2025

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.2-alpine

Name8.2.29-alpine3.22
Digestsha256:cdee2ae021443a0806843448eb174a188d6e6d85377a2e5a9bcd44161001fb8d
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed5 days ago
Size37 MB
Packages60
Flavoralpine
OS3.22
Runtime8.2.29
The base image is also available under the supported tag(s): 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

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

TagDetailsPushedVulnerabilities
8.4-alpine
Minor runtime version update
Also known as:
  • 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
Benefits:
  • 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
Image details:
  • Size: 42 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.11
5 days ago



8.3-alpine
Minor runtime version update
Also known as:
  • 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
Benefits:
  • 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
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.3.24
5 days ago



Copy link

github-actions bot commented Aug 6, 2025

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:65c973126d63a946cbbd43f193ae47598f3228197250b6136f91eae2a5a395a9
vulnerabilitiescritical: 1 high: 2 medium: 0 low: 0
platformlinux/amd64
size113 MB
packages249
📦 Base Image php:8.3-alpine
also known as
  • 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
digestsha256:f43a903b3e7fb97ce6ecdc8ab54c4beeebc913c38697740c6e9dd0d69fc37322
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

pkg:golang/golang.org/x/[email protected]

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th 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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

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.

critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/[email protected]

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

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.

Copy link

github-actions bot commented Aug 6, 2025

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.3-alpine

Name8.3.24-alpine3.22
Digestsha256:f43a903b3e7fb97ce6ecdc8ab54c4beeebc913c38697740c6e9dd0d69fc37322
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed5 days ago
Size37 MB
Packages60
Flavoralpine
OS3.22
Runtime8.3.24
The base image is also available under the supported tag(s): 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

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

TagDetailsPushedVulnerabilities
8.4-alpine
Minor runtime version update
Also known as:
  • 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
Benefits:
  • 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
Image details:
  • Size: 42 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.11
5 days ago



Copy link

github-actions bot commented Aug 6, 2025

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:b3ed7334ec4753eb0d80e6f0865fd87cd4aa1dd47223d16de5649670cf3ad937
vulnerabilitiescritical: 1 high: 2 medium: 0 low: 0
platformlinux/amd64
size118 MB
packages249
📦 Base Image php:8-alpine
also known as
  • 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
digestsha256:4ff5194e9fa697591425fa74e939879cde8c0d0da6a53b4b247cc47f43eb7d91
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

pkg:golang/golang.org/x/[email protected]

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th 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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

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.

critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/[email protected]

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

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.

Copy link

github-actions bot commented Aug 6, 2025

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:916d7361c0f20ed880e4bcdbb74829544f9cea1db691339ab5c8dd1251e693b1
vulnerabilitiescritical: 1 high: 2 medium: 0 low: 0
platformlinux/amd64
size137 MB
packages284
📦 Base Image php:8-alpine
also known as
  • 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
digestsha256:4ff5194e9fa697591425fa74e939879cde8c0d0da6a53b4b247cc47f43eb7d91
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

pkg:golang/golang.org/x/[email protected]

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th 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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

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.

critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/[email protected]

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

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.

Copy link

github-actions bot commented Aug 6, 2025

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8-alpine

Name8.4.11-alpine3.22
Digestsha256:4ff5194e9fa697591425fa74e939879cde8c0d0da6a53b4b247cc47f43eb7d91
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed5 days ago
Size42 MB
Packages60
Flavoralpine
OS3.22
Runtime8.4.11
The base image is also available under the supported tag(s): 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

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.

Copy link

github-actions bot commented Aug 6, 2025

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8-alpine

Name8.4.11-alpine3.22
Digestsha256:4ff5194e9fa697591425fa74e939879cde8c0d0da6a53b4b247cc47f43eb7d91
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed5 days ago
Size42 MB
Packages60
Flavoralpine
OS3.22
Runtime8.4.11
The base image is also available under the supported tag(s): 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

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: maintenance For maintenance, refactor and testing (perf, chore, style, revert, refactor, test, build, ci)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants