dbcve.org
MatchApplication · Anomali

CVE-2023-49329

HIGH · 7.2 CVSS v3.1 Published 2024-01-19
Fix available
A fix is available. Upgrade to 4.4.5 / 4.5.4 or later.
See remediation →
78/100
Remediation priority · High
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
Anomali Match before 4.6.2 allows OS Command Injection. An authenticated admin user can inject and execute operating system commands. This arises from improper handling of untrusted input, enabling an attacker to elevate privileges, execute system commands, and potentially compromise the underlying operating system. The fixed versions are 4.4.5, 4.5.4, and 4.6.2. The earliest affected version is 4.3.

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

Anomali Match before version 4.6.2 contains an OS command injection vulnerability that allows authenticated admin users to inject and execute arbitrary operating system commands through improper handling of untrusted input. This stems from insufficient input sanitization in application parameters that are passed to system call functions, enabling privilege escalation and potential full OS compromise.

MitigationUpgrade Anomali Match to version 4.6.2 (or 4.4.5/4.5.4 for older branches) to remediate this vulnerability. As an interim measure, restrict administrative access to only trusted personnel and monitor for suspicious command execution patterns.

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
MatchApplication
Affected:>= 4.3, < 4.4.5>= 4.5.0, < 4.5.4>= 4.6.0, < 4.6.2

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
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

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

  1. Confirm Anomali Match installation
    Locate the Anomali Match application in your environment. Check for installation directories, service processes, or the web interface typically accessible on port 8443 or 443.
    Affected if Anomali Match is not installed or not present in the environment
  2. Identify installed version
    Access the Anomali Match admin interface or check version files in the installation directory. Typically found in /opt/match/ or via the web UI under System > About or similar status page.
    Affected if Unable to determine the version from available configuration or admin interface
  3. Compare version against affected ranges
    The vulnerability affects: version 4.3 through 4.4.4, 4.5.0 through 4.5.3, and 4.6.0 through 4.6.1. Compare your identified version to these ranges.
    Affected if Installed version falls within any of these ranges: >= 4.3 and < 4.4.5, OR >= 4.5.0 and < 4.5.4, OR >= 4.6.0 and < 4.6.2
  4. Verify admin access exists
    Confirm the Anomali Match administrative interface is accessible and functional. This vulnerability requires authenticated admin privileges to exploit.
    Affected if Admin interface is accessible and the software version is in the affected ranges

You are affected if Anomali Match is installed and the installed version falls within 4.3 to 4.4.4, 4.5.0 to 4.5.3, or 4.6.0 to 4.6.1.

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 4.4.5 / 4.5.4 / 4.6.2 or later
Fixed in 4.4.54.5.44.6.2
Interim mitigation

Upgrade Anomali Match to version 4.6.2 (or 4.4.5/4.5.4 for older branches) to remediate this vulnerability. As an interim measure, restrict administrative access to only trusted personnel and monitor for suspicious command execution patterns.

Recommended fix High confidence

Upgrade to Anomali Match version 4.6.2 (or 4.4.5/4.5.4 depending on your starting version)

  1. 1. Identify the current installed version of Anomali Match by checking the application interface or system configuration.
  2. 2. Determine the appropriate upgrade path based on your current version (4.3 to 4.4.x should upgrade to 4.4.5; 4.5.x to 4.5.4; 4.6.0-4.6.1 to 4.6.2).
  3. 3. Create a complete backup of the Anomali Match database, configuration files, and any custom settings.
  4. 4. Review Anomali upgrade documentation for your specific version migration path.
  5. 5. Perform the upgrade to the fixed version (recommended: 4.6.2 as the latest stable release).
  6. 6. After upgrade, verify the application is operational and test that the command injection vulnerability is no longer present.
  7. 7. Review user accounts and permissions to ensure no unauthorized changes were made during the time the vulnerability was exploitable.

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

Fix this in Match Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49329 — 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-2023-49329 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