Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2022-36633

Vulnerability in github.com/gravitational/teleport (CVE-2022-36633)

Summary

Vulnerability in github.com/gravitational/teleport (CVE-2022-36633). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 10.1.2 or later.

Original description

The description as published by the source.

Teleport 9.3.6 is vulnerable to Command injection leading to Remote Code Execution. An attacker can craft a malicious ssh agent installation link by URL encoding a bash escape with carriage return line feed. This url encoded payload can be used in place of a token and sent to a user in a social engineering attack. This is fully unauthenticated attack utilizing the trusted teleport server to deliver the payload.

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-36633 has been found in github.com/gravitational/teleport.
Successful exploitation can lead to full system takeover.
What to do: upgrade github.com/gravitational/teleport to 10.1.2 or later.
If unsure, ask your IT team or search "github.com/gravitational/teleport CVE-2022-36633" on the vendor's site.

CVE-2022-36633 (github.com/gravitational/teleport) — CWE-20
Attack vector: remote (network-reachable) / unauthenticated
Patched: 10.1.2 — apply immediately
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.

❓ What is the problem

A vulnerability (CWE-20) exists in github.com/gravitational/teleport.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/gravitational/teleport.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 10.1.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/gravitational/teleport' . 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

  1. 1
    Identify exposure identify 
    grep -r 'github.com/gravitational/teleport' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/gravitational/teleport を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/gravitational/teleport to 10.1.2

    ステージング環境で 10.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/gravitational/teleport
[{"type":"SEMVER","events":[{"introduced":"10.0.0"},{"fixed":"10.1.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details