Vulnerability in go.pinniped.dev (CVE-2022-31677)
Summary
Vulnerability in go.pinniped.dev (CVE-2022-31677). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.19.0 or later.
Original description
The description as published by the source.
Impact
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.
Access tokens issued by the Pinniped Supervisor have an intended expiration lifetime of approximately two minutes. The Pinniped CLI will automatically use the refresh token, which has a lifetime of approximately nine hours, to request a new access token after the access token's advertised expiration time elapses. Starting in Pinniped version 0.13.0, the Supervisor performs checks during each refresh request against the configured external identity provider to determine if the user should be allowed to continue their session. Thus, the short lifetime of the access token is intended to force users to be subjected to those checks often. For example, if a user's account in the external identity provider became locked, the next refresh would fail, and the user should lose access to the Kubernetes clusters fairly quickly. As another example, if a user's group membership changed in the external identity provider, the new group memberships would be reflected in their sessions with Kubernetes clusters within a fairly short window of time.
Access tokens are cached in a local file by the Pinniped CLI (the kubectl plugin) and are sent back to the Supervisor (via HTTPS) to receive cluster-scoped credentials. Due to a bug in this token exchange, the expiration time of the submitte…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2022-31677 has been found in go.pinniped.dev.
Risk of unauthorized operations or information disclosure.
What to do: upgrade go.pinniped.dev to 0.19.0 or later.
If unsure, ask your IT team or search "go.pinniped.dev CVE-2022-31677" on the vendor's site.
CVE-2022-31677 (go.pinniped.dev) — CWE-613
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.19.0 — apply immediately
Workaround: There are no known workarounds.
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.
A vulnerability (CWE-613) exists in go.pinniped.dev.
Check the vendor advisory for the affected versions of go.pinniped.dev.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.19.0.
Workaround: There are no known workarounds.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'go.pinniped.dev' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'go.pinniped.dev' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
go.pinniped.devを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
There are no known workarounds.パッチが適用されるまでの応急処置として、There are no known workarounds. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade go.pinniped.dev to 0.19.0ステージング環境で 0.19.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com