Skip to content
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

Update module github.com/docker/docker to v24.0.7+incompatible [SECURITY] #371

Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 30, 2023

Mend Renovate logo banner

This PR contains the following updates:

Package Type Update Change
github.com/docker/docker require patch v24.0.6+incompatible -> v24.0.7+incompatible

GitHub Vulnerability Alerts

GHSA-jq35-85cj-fj4p

Intel's RAPL (Running Average Power Limit) feature, introduced by the Sandy Bridge microarchitecture, provides software insights into hardware energy consumption. To facilitate this, Intel introduced the powercap framework in Linux kernel 3.13, which reads values via relevant MSRs (model specific registers) and provides unprivileged userspace access via sysfs. As RAPL is an interface to access a hardware feature, it is only available when running on bare metal with the module compiled into the kernel.

By 2019, it was realized that in some cases unprivileged access to RAPL readings could be exploited as a power-based side-channel against security features including AES-NI (potentially inside a SGX enclave) and KASLR (kernel address space layout randomization). Also known as the PLATYPUS attack, Intel assigned CVE-2020-8694 and CVE-2020-8695, and AMD assigned CVE-2020-12912.

Several mitigations were applied; Intel reduced the sampling resolution via a microcode update, and the Linux kernel prevents access by non-root users since 5.10. However, this kernel-based mitigation does not apply to many container-based scenarios:

  • Unless using user namespaces, root inside a container has the same level of privilege as root outside the container, but with a slightly more narrow view of the system
  • sysfs is mounted inside containers read-only; however only read access is needed to carry out this attack on an unpatched CPU

While this is not a direct vulnerability in container runtimes, defense in depth and safe defaults are valuable and preferred, especially as this poses a risk to multi-tenant container environments running directly on affected hardware. This is provided by masking /sys/devices/virtual/powercap in the default mount configuration, and adding an additional set of rules to deny it in the default AppArmor profile.

While sysfs is not the only way to read from the RAPL subsystem, other ways of accessing it require additional capabilities such as CAP_SYS_RAWIO which is not available to containers by default, or perf paranoia level less than 1, which is a non-default kernel tunable.

References


Release Notes

docker/docker (github.com/docker/docker)

v24.0.7+incompatible

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@renovate renovate bot force-pushed the renovate/go-github.com/docker/docker-vulnerability branch 2 times, most recently from 01805d4 to 51de7f4 Compare November 6, 2023 16:45
@renovate renovate bot force-pushed the renovate/go-github.com/docker/docker-vulnerability branch 2 times, most recently from e0c959f to 88609a4 Compare November 10, 2023 15:17
@renovate renovate bot force-pushed the renovate/go-github.com/docker/docker-vulnerability branch 2 times, most recently from 5591289 to 47864b3 Compare November 17, 2023 10:45
@renovate renovate bot force-pushed the renovate/go-github.com/docker/docker-vulnerability branch from 47864b3 to 014b3cd Compare November 28, 2023 10:00
@renovate renovate bot force-pushed the renovate/go-github.com/docker/docker-vulnerability branch from 014b3cd to 5841b0b Compare November 28, 2023 10:37
@pablochacin
Copy link
Collaborator

Not relevant

Copy link
Contributor Author

renovate bot commented Nov 28, 2023

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v24.0.7+incompatible). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/go-github.com/docker/docker-vulnerability branch November 28, 2023 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants