dbcve.org
Pan OsOperating system · Paloaltonetworks

CVE-2012-6602

HIGH · 9.0 CVSS v2.0 Published 2013-08-31
Fix available
A fix is available. Upgrade to after 3.1.9 or later.
See remediation →
96/100
Remediation priority · Urgent
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
The device-management command-line interface in Palo Alto Networks PAN-OS before 3.1.10 and 4.0.x before 4.0.4 allows remote authenticated users to execute arbitrary commands via unspecified vectors, aka Ref ID 30122.

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 the PAN-OS device-management CLI allows remote authenticated users to execute arbitrary operating system commands due to insufficient input validation. The vulnerability affects PAN-OS versions before 3.1.10 and 4.0.x before 4.0.4.

MitigationUpgrade PAN-OS to version 3.1.10 or later, or 4.0.4 or later. Until patched, limit administrative access to trusted users only and monitor for suspicious CLI activity.

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
Pan OsOperating system
Affected:<= 3.1.9= 4.0.0= 4.0.1= 4.0.2= 4.0.3

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
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

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. Determine the installed PAN-OS version
    Access the device-management CLI and run the command to display system information, or check through the web interface under Device > Setup > Operations to view the software version
    Affected if The displayed version is 3.1.9 or lower, OR the version is 4.0.0, 4.0.1, 4.0.2, or 4.0.3
  2. Verify the device-management CLI is accessible
    Confirm that the PAN-OS CLI (command-line interface) is enabled and reachable via network access (SSH or console)
    Affected if CLI access is enabled and the system is networked (this is the attack surface for the vulnerability)
  3. Confirm remote authentication method
    Review the authentication settings for CLI access to determine if remote users can authenticate to the device
    Affected if Remote authentication is configured for administrative access to the CLI (remote authenticated users are the threat vector in this CVE)

You are affected if your PAN-OS version is 3.1.9 or earlier, or any version from 4.0.0 through 4.0.3, AND the device-management CLI is accessible to remote authenticated users.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.1.9
Interim mitigation

Upgrade PAN-OS to version 3.1.10 or later, or 4.0.4 or later. Until patched, limit administrative access to trusted users only and monitor for suspicious CLI activity.

Recommended fix High confidence

PAN-OS 3.1.10或更高版本；PAN-OS 4.0.4或更高版本（建议升级到各分支的最新稳定版）

  1. 1. Identify current PAN-OS version by logging into the device management interface and checking the Dashboard or running 'show system info' in the CLI
  2. 2. Download the fixed PAN-OS release from the Palo Alto Networks Support Portal (requires active support contract)
  3. 3. For PAN-OS 3.1.x systems: upgrade to PAN-OS 3.1.10 or later
  4. 4. For PAN-OS 4.0.x systems: upgrade to PAN-OS 4.0.4 or later
  5. 5. Review the PAN-OS Upgrade Guide and Release Notes for pre-upgrade compatibility checks
  6. 6.备份设备配置到本地或安全存储位置
  7. 7. 在非生产环境测试升级过程，验证关键功能正常运行
  8. 8. 在维护窗口期间执行升级，按照官方升级文档的步骤操作
Caveat 升级前需检查与当前设备型号的兼容性，并查看目标版本的发布说明了解可能的配置变更

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pan Os Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-6602 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2012-6602 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