OS Command InjectionWeakness · CWE-78

CVE-2022-20652

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability in the web-based management interface and in the API subsystem of Cisco Tetration could allow an authenticated, remote attacker to inject arbitrary commands to be executed with root-level privileges on the underlying operating system. This vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by submitting a crafted HTTP message to the affected system. A successful exploit could allow the attacker to execute commands with root-level privileges. To exploit this vulnerability, an attacker would need valid administrator-level credentials.Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

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 confidence

Command injection vulnerability in Cisco Tetration's web-based management interface and API subsystem. An authenticated attacker with administrator credentials can inject arbitrary OS commands through crafted HTTP requests due to insufficient input validation, achieving root-level code execution on the underlying operating system.

MitigationApply the Cisco software update to address this vulnerability. No workarounds are available. Since exploitation requires valid administrator-level credentials, ensure strong credential management and restrict administrative access to trusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco Tetration installation
    Locate Cisco Tetration components in your environment - check for tetration-related services, processes, or installed packages using system inventory tools or package managers
    Affected if Cisco Tetration software is present and running in the environment
  2. Verify web management interface is enabled
    Check if the Tetration web-based management interface or API subsystem is accessible and running, typically on configured management ports
    Affected if The web-based management interface or API is exposed and operational
  3. Confirm administrator accounts exist
    Review user account configuration in Tetration for administrator-level accounts, checking authentication settings and privilege levels
    Affected if Valid administrator-level credentials are configured in the system
  4. Check installed version against affected releases
    Retrieve the installed Cisco Tetration version from the system or administrative interface and compare against known vulnerable version ranges
    Affected if The installed version falls within the affected version range and all other conditions are met
  5. Review access controls on management interface
    Examine network access controls, firewall rules, and ACLs restricting access to the Tetration management interface
    Affected if The management interface is accessible from untrusted networks without sufficient restrictions

Environment is affected if Cisco Tetration with a vulnerable version is installed, the web management interface is accessible, and administrator credentials exist or could be obtained by an attacker.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco software update to address this vulnerability. No workarounds are available. Since exploitation requires valid administrator-level credentials, ensure strong credential management and restrict administrative access to trusted networks.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20652 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-20652 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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