CVE-2024-41228
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA symlink following vulnerability in the pouch cp function of AliyunContainerService pouch v1.3.1 allows attackers to escalate privileges and write arbitrary files.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA symlink following vulnerability exists in the 'pouch cp' command of AliyunContainerService pouch v1.3.1. The copy function does not properly validate or sanitize symlinks before following them, allowing attackers to manipulate symbolic links to traverse the filesystem and write arbitrary files to locations outside the intended target directory. Combined with the privilege escalation aspect, this enables attackers to gain elevated privileges by writing to sensitive locations such as cron jobs, startup scripts, or other privileged executables.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify pouch versionRun 'pouch version' or 'pouchd --version' to get the installed pouch version numberAffected if Version is 1.3.1 or falls below the fixed version that includes symlink validation fixes
-
Verify pouch cp command availabilityExecute 'pouch cp --help' to confirm the cp command is present and accessibleAffected if The cp command exists and is usable by the attacker or compromised account
-
Check access control on pouch cpReview ACLs, RBAC policies, or container execution policies to determine if untrusted users or processes can invoke the pouch cp commandAffected if Untrusted users or non-admin processes have permission to execute pouch cp
-
Monitor for symlink creationInspect container filesystem directories for recently created symlinks, especially in temporary or working directories used with pouch cp operationsAffected if Unexpected symlinks are found in directories where copy operations occur or in container root filesystems
You are affected if pouch version is 1.3.1 or unpatched, and the pouch cp command is accessible to untrusted users who could exploit symlink traversal for privilege escalation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade pouch to the latest version that includes proper symlink validation in the cp function. As an interim measure, restrict access to the pouch cp command to trusted users only and monitor for suspicious symlink creation in container filesystem operations.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41228 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-41228 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data