dbcve.org
Ansible Automation PlatformApplication · Redhat

CVE-2022-3205

MEDIUM · 6.1 CVSS v3.1 Published 2022-09-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross site scripting in automation controller UI in Red Hat Ansible Automation Platform 1.2 and 2.0 where the project name is susceptible to XSS injection

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

Stored cross-site scripting (XSS) vulnerability in the automation controller UI of Red Hat Ansible Automation Platform 1.2 and 2.0 where the project name field does not properly sanitize user input, allowing injection of malicious JavaScript that executes when other users view the project in the UI.

MitigationImplement strict input validation and output encoding for project name fields in the UI; upgrade to patched versions of Ansible Automation Platform when available from Red Hat.

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
Ansible Automation PlatformApplication
Affected:= 1.2= 2.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Ansible Automation Platform version
    Check the installed version of Red Hat Ansible Automation Platform in the system. This is typically visible in the UI header, the about page, or via the awx-manage command: awx-manage --version
    Affected if The installed version is exactly 1.2 or exactly 2.0
  2. Determine if you have project creation access
    Log into the Ansible Automation Platform controller UI and verify if your user account has permissions to create or edit projects. Navigate to Projects in the side menu and check if the Add button is available, or check your user role assignments.
    Affected if You have project creation or edit permissions in the controller UI
  3. Inspect existing project names for suspicious content
    Navigate to the Projects list in the automation controller UI. Review all project names for any that contain unusual characters such as <script>, javascript:, onload, onerror, or other HTML/JavaScript patterns. Click on each project to view its full details.
    Affected if Any project name contains raw HTML, JavaScript tags, or script-related patterns
  4. Check who can view the projects
    Examine the organization and permissions associated with each project. In the Projects view, click on a project and check the Organization field and access permissions to determine which other users or teams can view it in the UI.
    Affected if Projects with suspicious names are visible to users other than the project creator
  5. Review recent audit logs for project creation
    Access the Activity Stream or Audit logs in the automation controller. Look for recent project creation or modification events, particularly those with unusual timestamps or performed by users who typically do not create projects.
    Affected if There are unexpected project creation events in the audit logs

You are affected if you are running Ansible Automation Platform version 1.2 or 2.0 and have projects in the system that could contain malicious JavaScript in their names, which would execute when viewed by other users.

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

Implement strict input validation and output encoding for project name fields in the UI; upgrade to patched versions of Ansible Automation Platform when available from Red Hat.

Fix this in Ansible Automation Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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