{"answers":{"affected":"5 open source packages ship an affected version, including github.com/containerd/containerd.","exploited":"There is no known exploitation of GHSA-7ww5-4wqc-m92c in the wild and no public exploit code.","fix":"Upgrade github.com/containerd/containerd to a fixed version for your release line: 1.6.26 or 1.7.11.","what":"GHSA-7ww5-4wqc-m92c is a vulnerability in github.com/containerd/containerd, published on 19 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-7ww5-4wqc-m92c and fix it if it is affected.\n\nWhat it is: GHSA-7ww5-4wqc-m92c is a vulnerability in github.com/containerd/containerd, published on 19 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-7ww5-4wqc-m92c in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/containerd/containerd (Go): affected all versions; fixed in 1.6.26, 1.7.11\n- github.com/containerd/containerd (Go): affected all versions; fixed in 1.6.26\n- github.com/containerd/containerd (Go): affected all versions; fixed in 1.6.26\n- github.com/containerd/containerd (Go): affected from 1.7.0; fixed in 1.7.11\n- github.com/containerd/containerd (Go): affected from 1.7.0; fixed in 1.7.11\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-7ww5-4wqc-m92c/ (Markdown: https://insights.sbomify.com/GHSA-7ww5-4wqc-m92c/index.md)","id":"GHSA-7ww5-4wqc-m92c","markdown":"https://insights.sbomify.com/GHSA-7ww5-4wqc-m92c/index.md","name":"GHSA-7ww5-4wqc-m92c","record":{"aliases":["GO-2023-2412"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"configuration_change","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"container runtime","requires_auth":"low_privilege","summary":"Attackers with container access can read RAPL power data to perform side-channel attacks against AES-NI and KASLR, bypassing kernel mitigations.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"# /sys/devices/virtual/powercap accessible by default to containers\n\nIntel'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.\n\nBy 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](https://platypusattack.com/), Intel assigned [CVE-2020-8694](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8694) and [CVE-2020-8695](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8695), and AMD assigned [CVE-2020-12912](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12912).\n\nSeveral mitigations were applied; Intel reduced the sampling resolution via a microcode update, and the Linux kernel [prevents access by non-root users](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=949dd0104c496fa7c14991a23c03c62e44637e71) since 5.10. However, this kernel-based mitigation does not apply to many container-based scenarios:\n* 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\n* `sysfs` is mounted inside containers read-only; however only read access is needed to carry out this attack on an unpatched CPU\n\nWhile 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. 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.\n\nWhile `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.\n\n## References\n\n* https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8694\n* https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8695\n* https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12912\n* https://platypusattack.com/\n* https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=949dd0104c496fa7c14991a23c03c62e44637e71\n* https://web.eece.maine.edu/~vweaver/projects/rapl/","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"containerd allows RAPL to be accessible to a container","id":"GHSA-7ww5-4wqc-m92c","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":5,"n_references":null,"packages":[{"ecosystem":"Go","fixed":["1.6.26","1.7.11"],"introduced":["0","1.7.0"],"last_affected":[],"package":"github.com/containerd/containerd","purl":"pkg:golang/github.com/containerd/containerd","source":"GO-2023-2412"},{"ecosystem":"Go","fixed":["1.6.26"],"introduced":["0"],"last_affected":[],"package":"github.com/containerd/containerd","purl":null,"source":"GHSA-7ww5-4wqc-m92c"},{"ecosystem":"Go","fixed":["1.6.26"],"introduced":["0"],"last_affected":[],"package":"github.com/containerd/containerd","purl":"pkg:golang/github.com/containerd/containerd","source":"GHSA-7ww5-4wqc-m92c"},{"ecosystem":"Go","fixed":["1.7.11"],"introduced":["1.7.0"],"last_affected":[],"package":"github.com/containerd/containerd","purl":null,"source":"GHSA-7ww5-4wqc-m92c"},{"ecosystem":"Go","fixed":["1.7.11"],"introduced":["1.7.0"],"last_affected":[],"package":"github.com/containerd/containerd","purl":"pkg:golang/github.com/containerd/containerd","source":"GHSA-7ww5-4wqc-m92c"}],"products":null,"published":"2023-12-19","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers with container access can read RAPL power data to perform side-channel attacks against AES-NI and KASLR, bypassing kernel mitigations.","url":"https://insights.sbomify.com/GHSA-7ww5-4wqc-m92c/"}