← Back
UBUNTU-CVE-2023-30549
Vulnerability in singularity-container (UBUNTU-CVE-2023-30549)
Summary
vulnerability in singularity-container (UBUNTU-CVE-2023-30549). Risk of unauthorized operations or information disclosure.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **UBUNTU-CVE-2023-30549** has been found in singularity-container.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "singularity-container UBUNTU-CVE-2023-30549" on the vendor's site.
UBUNTU-CVE-2023-30549 (singularity-container) —
Attack vector: local / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (unclassified) exists in singularity-container.
📍 Affected scope
singularity-container — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'singularity-container' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'singularity-container' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `singularity-container` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:18.04:LTS
singularity-container
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:Pro:24.04:LTS
singularity-container
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:25.10
singularity-container
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:26.04:LTS
singularity-container
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- report https://ubuntu.com/security/CVE-2023-30549
- report https://github.com/apptainer/apptainer/security/advisories/GHSA-j4rf-7357-f4cg
- report https://access.redhat.com/security/cve/cve-2022-1184
- report https://www.suse.com/security/cve/CVE-2022-1184.html
- report https://ubuntu.com/security/CVE-2022-1184
- report https://github.com/apptainer/apptainer/commit/5a4964f5ba9c8d89a0e353b97f51fd607670a9f7
- report https://security-tracker.debian.org/tracker/CVE-2022-1184
- report https://github.com/apptainer/apptainer/releases/tag/v1.1.8
- report https://www.cve.org/CVERecord?id=CVE-2023-30549