CVE-2024-53351
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 · uneditedInsecure permissions in pipecd v0.49 allow attackers to gain access to the service account's token, leading to escalation of privileges.
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 · low confidenceIn pipecd v0.49, insecure permissions on a specific component or API endpoint allow unauthenticated or low-privilege attackers to access service account tokens. This token exposure enables privilege escalation to higher system permissions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.49.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Check the installed pipecd versionRun the command `piped --version` or check the version of the pipecd container/image that is deployed. If using Kubernetes, check the image tag in your deployment manifests.Affected if The installed version is 0.49.3 or any earlier version within the 0.49.x line (e.g., 0.49.0, 0.49.1, 0.49.2).
-
Identify service account configuration storageLocate where pipecd stores or references service account credentials. Check configuration files (typically in the control plane and piped components) for entries related to service accounts, API keys, or tokens. Look in configuration directories such as /etc/piped, ~/.piped, or the helm/chart values if deployed via Kubernetes.Affected if Service account tokens or credentials are stored in locations accessible to users with standard authenticated access, without additional access restrictions.
-
Verify file and directory permissions on credential storageRun `ls -la` or `getfacl` on directories and files containing service account tokens. Check if permissions allow read access to users other than the dedicated pipecd service account or root. For Kubernetes deployments, check RBAC policies and pod security contexts.Affected if Permissions on service account token files or directories are set to 644, 755, or any mode that grants read access to non-owner users, or if RBAC policies allow authenticated users to read secrets.
-
Check for overly permissive access controlsReview pipecd's RBAC configuration, API access controls, and any defined roles. Verify whether standard authenticated users (non-admin) can access the service accounts API endpoint or resource. In Kubernetes, check if users can list or get secrets in namespaces where piped runs.Affected if Standard authenticated users have permission to list, get, or otherwise access service account resources or secrets beyond what is required for their role.
Your environment is affected if you are running pipecd version 0.49.0 through 0.49.3 AND the service account token storage or API access controls permit read access to users beyond the intended service account owner.
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 dataReview and restrict permissions on all pipecd components to principle of least privilege; rotate any exposed service account tokens immediately; upgrade to patched version if available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-53351 — 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-53351 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