ContourApplication · Projectcontour
CVE-2024-36539
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 contour v1.28.3 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.
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 confidenceInsecure permissions in Contour v1.28.3 allow attackers to obtain the service account's token, enabling access to sensitive data and privilege escalation within the Kubernetes cluster.
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
ContourApplication
= 1.28.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.
-
Verify Contour version is 1.28.3Run `kubectl get deployment contour -n projectcontour -o jsonpath='{.spec.template.spec.containers[0].image}'` or check the image tag in your Contour deploymentAffected if The Contour image version is exactly 1.28.3 (older or newer versions are not affected by this specific CVE)
-
Check file system permissions on Contour pod volumesExec into the Contour pod and inspect permissions on mounted volumes: `kubectl exec -n projectcontour deploy/contour -- ls -la /` and check for world-readable directories or files containing service account tokensAffected if Files or directories in the Contour pod filesystem have overly permissive settings (e.g., 777 or world-readable) that allow unauthorized access to service account credentials
-
Inspect Contour service account RBAC bindingsRun `kubectl get serviceaccount contour -n projectcontour -o yaml` and `kubectl get rolebinding,clusterrolebinding -n projectcontour --as=system:serviceaccount:projectcontour:contour -o yaml` to review what permissions the Contour service account hasAffected if The Contour service account has been granted excessive RBAC permissions that allow it to access secrets or other sensitive resources beyond its intended scope
-
Check for readable service account tokens in the Contoy deploymentReview the Contour pod spec for mounted service account tokens: `kubectl get pod -n projectcontour -l app=contour -o jsonpath='{.items[*].spec.serviceAccountName}'` and verify tokens are not exposed via configmaps or secrets with weak permissionsAffected if The Contour service account token is accessible to unauthorized users or processes due to insecure permissions on the token file or its parent directory
You are affected if running Contour version 1.28.3 AND the Contour deployment has insecure file system or RBAC permissions that expose the service account token to unauthorized access.
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 harden file system and RBAC permissions for the Contour deployment, ensuring service account tokens are not accessible to unauthorized users or processes.
Fix this in Contour
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36539 — 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-36539 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