dbcve.org
Aria AutomationApplication · VMware

CVE-2024-22280

HIGH · 8.1 CVSS v3.1 Published 2024-07-11
Fix available
A fix is available. Upgrade to 8.17.0 or later.
See remediation →
87/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
VMware Aria Automation does not apply correct input validation which allows for SQL-injection in the product. An authenticated malicious user could enter specially crafted SQL queries and perform unauthorised read/write operations in the database.

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

VMware Aria Automation contains a SQL injection vulnerability due to improper input validation. An authenticated attacker with user-level access can inject malicious SQL queries through input fields, potentially allowing unauthorized read/write operations on the underlying database.

MitigationApply the vendor-provided patch for CVE-2024-22280 as soon as possible. As an interim control, restrict database access permissions for application service accounts to principle of least privilege and consider deploying a WAF rule to detect SQL injection 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
Aria AutomationApplication
Affected:< 8.17.0
Cloud FoundationApplication
Affected:>= 4.0, <= 5.0

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

CVSS:3.1/AV:N/AC:L/PR:L/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 installed VMware Aria Automation version
    Use the VMware Aria Automation admin interface or run 'vracli version' from the appliance console to retrieve the exact version number
    Affected if The installed version is lower than 8.17.0
  2. Identify installed VMware Cloud Foundation version
    Access the VMware Cloud Foundation management interface or run 'sddc-manager --version' from the SDDC Manager to get the version number
    Affected if The installed version is between 4.0 and 5.0 inclusive (>= 4.0 and <= 5.0)
  3. Verify the product is deployed and running
    Confirm the VMware Aria Automation or VMware Cloud Foundation services are active and the web-based management interface is accessible
    Affected if The product is running and exposed on the network, making it accessible to authenticated users
  4. Confirm user authentication is enabled
    Check that the local user accounts or external identity provider integration is configured and functional in the VMware Aria Automation authentication settings
    Affected if User-level authentication is active, which is required for the attacker to exploit the SQL injection flaw

The environment is affected if either VMware Aria Automation version is below 8.17.0 or VMware Cloud Foundation version is between 4.0 and 5.0, and the product is deployed with user authentication enabled.

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 8.17.0 or later
Fixed in 8.17.0
Interim mitigation

Apply the vendor-provided patch for CVE-2024-22280 as soon as possible. As an interim control, restrict database access permissions for application service accounts to principle of least privilege and consider deploying a WAF rule to detect SQL injection patterns.

Recommended fix High confidence

Aria Automation 8.17.0 or later

  1. Review the VMware Aria Automation upgrade documentation at support.broadcom.com
  2. Verify current installed version of Aria Automation or Cloud Foundation
  3. Schedule a maintenance window for the upgrade
  4. Take a complete backup of the current Aria Automation environment including database
  5. Download VMware Aria Automation version 8.17.0 or later from Broadcom Support Portal
  6. Follow the documented upgrade procedure to upgrade Aria Automation to version 8.17.0
  7. For Cloud Foundation customers, upgrade to a version that includes the Aria Automation 8.17.0 fix
  8. After upgrade, verify the SQL injection vulnerability is resolved by confirming the version number
Caveat Review release notes for any known issues or configuration changes required when upgrading to 8.17.0

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

Fix this in Aria Automation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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