dbcve.org
Ca Automic AutomationApplication · Broadcom

CVE-2022-33750

CRITICAL · 9.8 CVSS v3.1 Published 2022-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
CA Automic Automation 12.2 and 12.3 contain an authentication error vulnerability in the Automic agent that could allow a remote attacker to potentially execute arbitrary commands.

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 · moderate confidence

CA Automic Automation 12.2 and 12.3 contain an authentication error vulnerability in the Automic agent component that allows remote attackers to bypass authentication mechanisms and potentially execute arbitrary commands on affected systems.

MitigationUpgrade to the latest version of Automic Automation that addresses this vulnerability, or apply vendor-supplied patches. Prioritize patching externally-facing agents and implement network segmentation to limit agent exposure.

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
Ca Automic AutomationApplication
Affected:= 12.2= 12.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
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 checks

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

  1. Identify Automic Automation installation
    Locate the Automic installation directory and check for version file (version.txt, version.properties, or similar). Common paths: /opt/automic or C:\Automic on Windows. Run command: ls -la <install_dir>/automationplatform/ or check Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Automic
    Affected if Installed version is exactly 12.2 or 12.3
  2. Verify agent component version
    Check the agent component version specifically. Navigate to the agent directory (typically <install_dir>/agents/ or check the agent executable properties). On Unix: ./ucxjlx6 -version. On Windows: ucxjlx6.exe -version
    Affected if Agent version reports exactly 12.2.x or 12.3.x
  3. Confirm agent service is running
    Check if the Automic agent process is active. On Unix: ps -ef | grep -i ucxjl. On Windows: sc query ucxj or check Task Manager for ucxjl* processes
    Affected if Agent process is running and version is 12.2 or 12.3
  4. Check agent network exposure
    Review agent configuration file (ucxjlx6.ini or agent.ini) for TCP/IP listener settings. Look for 'TCP_PORT' parameter and determine if the agent bind address is accessible externally (0.0.0.0 vs 127.0.0.1)
    Affected if Agent TCP port is bound to 0.0.0.0 or an external interface and version is 12.2 or 12.3
  5. Inspect authentication configuration
    Examine agent authentication settings in the agent configuration file or the Automic Automic Administration (ARA) console. Check if default credentials or weak authentication is configured for the agent
    Affected if Agent uses default authentication settings and version is 12.2 or 12.3

Environment is affected if Automic Automation agent version is exactly 12.2 or 12.3 and the agent component is running and network-accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the latest version of Automic Automation that addresses this vulnerability, or apply vendor-supplied patches. Prioritize patching externally-facing agents and implement network segmentation to limit agent exposure.

Recommended fix Moderate confidence

Latest stable Automic Automation 12.3.x release (check Broadcom support for exact patched version)

  1. 1. Review the latest release notes and security advisories on support.broadcom.com for CVE-2022-33750
  2. 2. Identify the specific patched release for Automic Automation 12.x (typically a 12.3.x maintenance release)
  3. 3. Plan upgrade during a maintenance window to minimize business impact
  4. 4. Backup current Automic Automation configuration and database
  5. 5. Stop all Automic services including the agent components
  6. 6. Upgrade Automic Automation to the latest patched 12.3.x release or the next stable release
  7. 7. Verify the agent component is updated to the matching patched version
  8. 8. Restart Automic services and validate the automation platform is operational
Caveat Review compatibility matrix for 12.3.x releases; ensure all integrations and custom scripts are tested against the target version before production deployment

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

Fix this in Ca Automic Automation Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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