Publish Advisories

GHSA-2cgq-h8xw-2v5j
GHSA-4jrx-5w4h-3gpm
GHSA-jxgr-gcj5-cqqg

advisories/github-reviewed/2024/04/GHSA-2cgq-h8xw-2v5j/GHSA-2cgq-h8xw-2v5j.json

@@ -1,13 +1,13 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-2cgq-h8xw-2v5j",
-  "modified": "2024-04-30T09:39:38Z",
+  "modified": "2024-05-01T13:06:49Z",
   "published": "2024-04-30T09:39:38Z",
   "aliases": [
     "CVE-2024-3154"
   ],
   "summary": "CRI-O vulnerable to an arbitrary systemd property injection",
-  "details": "### Impact\nOn CRI-O, an arbitrary systemd property can be injected via a Pod annotation:\n```\n---\napiVersion: v1\nkind: Pod\nmetadata:\n  name: poc-arbitrary-systemd-property-injection\n  annotations:\n    # I believe that ExecStart with an arbitrary command works here too,\n    # but I haven't figured out how to marshalize the ExecStart struct to gvariant string.\n    org.systemd.property.SuccessAction: \"'poweroff-force'\"\nspec:\n  containers:\n    - name: hello\n      image: [quay.io/podman/hello](http://quay.io/podman/hello)\n```\n\nThis means that any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system.\n\nTested with CRI-O v1.24 on minikube.\n\nThanks to Cédric Clerget (GitHub ID @cclerget) for finding out that CRI-O just passes pod annotations to OCI annotations:\nhttps://github.com/opencontainers/runc/pull/3923#discussion_r1532292536\n\nCRI-O has to filter out annotations that have the prefix \"org.systend.property.\"\n\nSee also:\n- https://github.com/opencontainers/runtime-spec/blob/main/features.md#unsafe-annotations-in-configjson\n- https://github.com/opencontainers/runc/pull/4217\n\n\n### Workarounds\nUnfortunately, the only workarounds would involve an external mutating webhook to disallow these annotations",
+  "details": "### Impact\nOn CRI-O, it looks like an arbitrary systemd property can be injected via a Pod annotation:\n```\n---\napiVersion: v1\nkind: Pod\nmetadata:\n  name: poc-arbitrary-systemd-property-injection\n  annotations:\n    # I believe that ExecStart with an arbitrary command works here too,\n    # but I haven't figured out how to marshalize the ExecStart struct to gvariant string.\n    org.systemd.property.SuccessAction: \"'poweroff-force'\"\nspec:\n  containers:\n    - name: hello\n      image: [quay.io/podman/hello](http://quay.io/podman/hello)\n```\n\nThis means that any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system.\n\nTested with CRI-O v1.24 on minikube.\nI didn't test the latest v1.29 because it is incompatible with minikube: https://github.com/kubernetes/minikube/pull/18367\n\nThanks to Cédric Clerget (GitHub ID @cclerget) for finding out that CRI-O just passes pod annotations to OCI annotations:\nhttps://github.com/opencontainers/runc/pull/3923#discussion_r1532292536\n\nCRI-O has to filter out annotations that have the prefix \"org.systemd.property.\"\n\nSee also:\n- https://github.com/opencontainers/runtime-spec/blob/main/features.md#unsafe-annotations-in-configjson\n- https://github.com/opencontainers/runc/pull/4217\n\n\n### Workarounds\nUnfortunately, the only workarounds would involve an external mutating webhook to disallow these annotations\n\n### References\n\n",
   "severity": [
     {
       "type": "CVSS_V3",

advisories/github-reviewed/2024/05/GHSA-4jrx-5w4h-3gpm/GHSA-4jrx-5w4h-3gpm.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-4jrx-5w4h-3gpm",
-  "modified": "2024-05-01T08:29:48Z",
+  "modified": "2024-05-01T13:07:04Z",
   "published": "2024-05-01T08:29:48Z",
   "aliases": [
     "CVE-2024-32963"
@@ -40,6 +40,10 @@
       "type": "WEB",
       "url": "https://github.com/navidrome/navidrome/security/advisories/GHSA-4jrx-5w4h-3gpm"
     },
+    {
+      "type": "ADVISORY",
+      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-32963"
+    },
     {
       "type": "PACKAGE",
       "url": "https://github.com/navidrome/navidrome"
@@ -52,6 +56,6 @@
     "severity": "MODERATE",
     "github_reviewed": true,
     "github_reviewed_at": "2024-05-01T08:29:48Z",
-    "nvd_published_at": null
+    "nvd_published_at": "2024-05-01T07:15:40Z"
   }
 }