dbcve.org
Ca Automic AutomationApplication · Broadcom

CVE-2022-33755

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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 insecure input handling vulnerability in the Automic Agent that could allow a remote attacker to potentially enumerate users.

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 versions 12.2 and 12.3 contain an insecure input handling vulnerability in the Automic Agent component. This vulnerability allows remote attackers to potentially enumerate valid users in the system through malformed or crafted input to the agent, likely by observing different responses for valid versus invalid usernames.

MitigationApply vendor patches for CVE-2022-33755 when available; until then, consider network segmentation to restrict access to the Automic Agent interface and implement additional monitoring for anomalous user enumeration 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
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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Automic Automation installation
    Check for installed Automic Automation components. On Windows, look in Program Files for 'Automic' directory, or check Windows Services for 'Automic' or 'Automation' services. On Unix/Linux, check common paths like /opt/automic or search for processes named 'automation' or 'automic'. Query the version using the embedded version info in executable files or check the installation directory for a version file.
    Affected if Version 12.2 or 12.3 is installed on the system
  2. Locate and verify the Automic Agent component
    Check running processes for the Automic Agent service or daemon. The agent process typically runs as a Windows service named 'Automic Agent' or a Unix daemon. Search for process names containing 'agent' in the Automic installation directory. Review the Agent configuration files in the agent's /bin or /conf directory.
    Affected if The Automic Agent component is installed and running
  3. Determine Agent network exposure
    Review the Agent configuration file (typically agent_name.ini or ucxjlx6.ini in the Agent/conf directory) for the 'port' setting. Use netstat or ss to verify which network interfaces and ports the Agent process is listening on. Check if the agent port is bound to 0.0.0.0 (all interfaces) versus 127.0.0.1 (localhost only).
    Affected if The Agent is listening on a network-accessible interface (0.0.0.0) rather than localhost only
  4. Verify Agent authentication settings
    Examine the Agent configuration file for authentication-related settings. Look for parameters controlling whether authentication is required for agent communications. Check if the 'secure' or 'authentication' flags are disabled or set to allow unauthenticated access.
    Affected if Agent authentication is disabled or not enforced for incoming connections

The environment is affected if Automic Automation version 12.2 or 12.3 is installed with the Agent component running and exposed to network traffic, allowing unauthenticated remote attackers to enumerate valid system users through malformed input.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for CVE-2022-33755 when available; until then, consider network segmentation to restrict access to the Automic Agent interface and implement additional monitoring for anomalous user enumeration patterns.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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