dbcve.org
OpenstackApplication · Redhat

CVE-2022-1655

MEDIUM · 6.5 CVSS v3.1 Published 2022-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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
An Incorrect Permission Assignment for Critical Resource flaw was found in Horizon on Red Hat OpenStack. Horizon session cookies are created without the HttpOnly flag despite HorizonSecureCookies being set to true in the environmental files, possibly leading to a loss of confidentiality and integrity.

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

Horizon session cookies in Red Hat OpenStack are created without the HttpOnly flag even when HorizonSecureCookies is configured to true in environment files. The HttpOnly flag prevents JavaScript access to cookies, so its absence could allow attackers who achieve XSS to steal session cookies, leading to session hijacking and loss of confidentiality and integrity.

MitigationConfigure Horizon to properly set the HttpOnly flag on session cookies, or apply the relevant Red Hat patch to ensure HorizonSecureCookies configuration correctly enables HttpOnly in addition to Secure flags.

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
OpenstackApplication
Affected:= 16.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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Verify OpenStack version
    Run 'openstack version' or check /etc/rhosp-version or the Red Hat OpenStack Platform version file to confirm the installed version is 16.2
    Affected if The installed version is Red Hat OpenStack 16.2
  2. Locate Horizon configuration
    Find the Horizon configuration file (typically /etc/openstack-dashboard/local_settings or /etc/horizon/horizon.conf) and check for the HorizonSecureCookies setting
    Affected if HorizonSecureCookies is set to true in the configuration
  3. Inspect Horizon session cookie configuration
    In the Horizon settings file, verify the SESSION_COOKIE_HTTPONLY setting - check if it is explicitly set to True, or if it inherits a default value
    Affected if SESSION_COOKIE_HTTPONLY is not explicitly set to True, or HorizonSecureCookies configuration does not properly enable HttpOnly
  4. Capture and examine a live Horizon session cookie
    Log into the Horizon dashboard and use browser developer tools (Application > Cookies) or run a curl command to capture the session cookie, then inspect the Set-Cookie header for the presence of the HttpOnly attribute
    Affected if The session cookie does not contain the HttpOnly flag despite HorizonSecureCookies being configured to true

A user is affected if they are running Red Hat OpenStack 16.2 and their Horizon session cookies are missing the HttpOnly flag even when HorizonSecureCookies is configured to true.

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

Configure Horizon to properly set the HttpOnly flag on session cookies, or apply the relevant Red Hat patch to ensure HorizonSecureCookies configuration correctly enables HttpOnly in addition to Secure flags.

Recommended fix Moderate confidence
  1. 1. Verify the current HorizonSecureCookies setting in the OpenStack environment configuration files (typically in /etc/openstack-dashboard/local_settings or environment-specific YAML files)
  2. 2. Ensure HorizonSecureCookies is explicitly set to true in the configuration
  3. 3. Review the Horizon settings.py or local_settings.py for the SESSION_COOKIE_HTTPONLY configuration parameter
  4. 4. Explicitly set SESSION_COOKIE_HTTPONLY = True in the Horizon configuration to ensure the HttpOnly flag is applied to session cookies
  5. 5. Restart Horizon services (httpd or apache2) after configuration changes
  6. 6. Verify that session cookies now include the HttpOnly flag by inspecting the Set-Cookie header in browser developer tools or using curl

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

Fix this in Openstack Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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