PinnipedApplication · VMware
CVE-2022-31677
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 · uneditedAn Insufficient Session Expiration issue was discovered in the Pinniped Supervisor (before v0.19.0). A user authenticating to Kubernetes clusters via the Pinniped Supervisor could potentially use their access token to continue their session beyond what proper use of their refresh token might allow.
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 · high confidenceIn the Pinniped Supervisor before v0.19.0, the session expiration logic is insufficient. Users authenticating to Kubernetes clusters can continue their session beyond the intended lifetime by using their access token directly, bypassing the proper refresh token mechanism that should enforce session limits.
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
PinnipedApplication
>= 0.3.0, < 0.19.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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 Pinniped Supervisor deploymentRun 'kubectl get deployments -A | grep -i pinniped' or 'kubectl get pods -A | grep -i supervisor' to find Pinniped Supervisor pods in the clusterAffected if No Pinniped Supervisor is found (not vulnerable as it's not installed)
-
Check Pinniped Supervisor versionRun 'kubectl get deployment -n <pinniped-namespace> pinniped-supervisor -o jsonpath='{.spec.template.spec.containers[0].image}' to get the image, then extract the version from the tagAffected if The version is 0.3.0 or higher but lower than 0.19.0 (e.g., v0.18.0, v0.15.0, v0.4.0)
-
Verify session token configurationCheck the Pinniped Supervisor configuration for how access tokens and refresh tokens are handled - inspect the Supervisor's configmap or custom resources in the pinniped namespaceAffected if Access tokens can be used directly without enforced refresh token expiration checks (typically indicated by lack of proper session lifetime enforcement in the configuration)
The environment is affected if Pinniped Supervisor is deployed with a version between 0.3.0 and 0.19.0 inclusive, and the configuration allows direct access token usage that can bypass intended session expiration limits.
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.
dbcve · scoped0.19.0
Upgrade Pinniped Supervisor to v0.19.0 or later, which contains the fix for proper session expiration enforcement.
v0.19.0
- Identify the current Pinniped Supervisor version running in your cluster
- Review the Pinniped release notes for v0.19.0 to understand any configuration or migration requirements
- Plan the upgrade window and backup current configuration
- Upgrade the Pinniped Supervisor to version v0.19.0 or later using your Kubernetes deployment method (e.g., helm upgrade, kubectl apply, or OLM)
- Verify the new version is running: kubectl get deployment -n pinniped-supervisor
- Test authentication flow to confirm the session expiration fix is working correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pinniped
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31677 — 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-2022-31677 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