Security readout for executives and security teams
Plain-English summary
Certain PAN-OS versions can write administrator usernames, passwords, and API keys into web server logs when the XML API is used incorrectly. The business risk is credential exposure to people or systems with log access. Exposure is narrower than an internet-wide remote bug, but affected environments should treat any logged secrets as compromised.
Executive priority
Prioritize for firewalls using PAN-OS XML API, especially where logs are aggregated or broadly accessible. The CVSS score is medium, but administrator credential exposure can create serious follow-on risk if logs were retained, exported, or readable by more users than intended.
Technical view
CVE-2021-3036 is CWE-532 information exposure in PAN-OS 8.1, 9.0, 9.1, and 10.0. It applies only when the PAN-OS XML API is configured and a client includes a duplicate API parameter. The vulnerable behavior logs administrator credentials and API keys in cleartext. CVSS 3.1 is 4.4, with local access and high privileges reflected in the vector.
Likely exposure
Most likely exposure is PAN-OS appliances running affected versions with XML API integrations or automation. Environments without XML API use are not described as affected. The main downstream risk is misuse of exposed administrator secrets from web server logs.
Exploitation context
The source bundle does not identify active exploitation, and KEV status is false. The issue depends on specific API use and subsequent access to cleartext web server logs. Evidence is insufficient to claim public exploitation or a broadly weaponized campaign.
Researcher notes
Scope is explicitly conditional: affected PAN-OS versions, XML API enabled, and duplicate API parameter in client requests. The source bundle does not provide fixed version details. Avoid assuming remote exploitability; focus validation on configuration, API client behavior, log contents, and credential rotation evidence.
Mitigation direction
- Identify PAN-OS 8.1, 9.0, 9.1, and 10.0 appliances using the XML API.
- Review XML API clients and integrations for duplicate API parameter behavior.
- Search web server logs for exposed administrator usernames, passwords, and API keys.
- Rotate any administrator passwords or API keys that may have been logged.
- Restrict access to PAN-OS web server logs to required administrators only.
- Check Palo Alto Networks advisory for official fixed versions and remediation guidance.
Validation and detection
- Confirm PAN-OS version and whether XML API is configured on each appliance.
- Inventory automation, scripts, and integrations that call the PAN-OS XML API.
- Review relevant web server logs for cleartext administrator secrets.
- Verify exposed API keys were revoked and replaced.
- Verify affected administrator passwords were changed.
- Document that current sources do not show KEV-listed exploitation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-532: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-3036 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N0.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.4MediumVector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://security.paloaltonetworks.com/CVE-2021-3036CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insertion of Sensitive Information into Log File
Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.