Cortex Xsoar CommonscriptsApplication · Paloaltonetworks
CVE-2024-5914
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 · uneditedA command injection issue in Palo Alto Networks Cortex XSOAR CommonScripts Pack allows an unauthenticated attacker to execute arbitrary commands within the context of an integration container.
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 confidenceA command injection vulnerability exists in the Palo Alto Networks Cortex XSOAR CommonScripts Pack that allows unauthenticated attackers to execute arbitrary commands within the context of an integration container. This critical flaw enables remote code execution at the container level without any authentication credentials.
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
Cortex Xsoar CommonscriptsApplication
< 1.12.33CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify CommonScripts Pack versionAccess Cortex XSOAR Marketplace or navigate to Settings > Advanced > Marketplace and check the installed version of the CommonScripts packAffected if The installed version is lower than 1.12.33
-
Confirm integration containers are in useCheck Cortex XSOAR integration settings by navigating to Settings > Integrations > Instances and review which integrations are configured to run in Docker containersAffected if Integration instances are configured to use containerized execution (Docker-based runners)
-
Review audit logs for suspicious script executionNavigate to Audit Logs (Settings > Monitoring > Audit) and search for entries involving script execution or command invocation from the CommonScripts pack, focusing on unusual or unexpected commandsAffected if Audit logs show execution of scripts from CommonScripts that contain unexpected shell commands or arguments not matching expected behavior
A user is affected if Cortex XSOAR has CommonScripts Pack installed at a version below 1.12.33 and integration containers are enabled and utilized for script execution.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.12.33
Apply the vendor-supplied patch to the Cortex XSOAR CommonScripts Pack as soon as possible; until patched, consider disabling or restricting access to affected integration containers to limit exposure.
Cortex XSOAR CommonScripts Pack version 1.12.33 or later
- Access the Cortex XSOAR Marketplace or Administration interface
- Navigate to the CommonScripts Pack
- Check current installed version - if below 1.12.33, an update is available
- Upgrade to version 1.12.33 or later
- Verify the upgrade completed successfully
- Confirm the new version is reflected in the Commonscripts Pack
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cortex Xsoar Commonscripts
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5914 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5914 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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