dbcve.org
HawkApplication · Tibco

CVE-2022-41564

MEDIUM · 6.5 CVSS v3.1 Published 2023-02-14
Fix available
A fix is available. Upgrade to 6.2.2 / 7.2.1 or later.
See remediation →
71/100
Remediation priority · Elevated
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
The Hawk Console component of TIBCO Software Inc.'s TIBCO Hawk and TIBCO Operational Intelligence Hawk RedTail contains a vulnerability that will return the EMS transport password and EMS SSL password to a privileged user. Affected releases are TIBCO Software Inc.'s TIBCO Hawk: versions 6.1.0 through 6.2.1 and TIBCO Operational Intelligence Hawk RedTail: versions 7.0.0 through 7.2.0.

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

The Hawk Console component in TIBCO Hawk (6.1.0-6.2.1) and TIBCO Operational Intelligence Hawk RedTail (7.0.0-7.2.0) contains an information disclosure vulnerability that returns EMS transport password and EMS SSL password to privileged users. This allows authenticated privileged users to obtain sensitive credential data they should not have direct access to.

MitigationApply vendor patches for the affected versions. Until patches are applied, restrict Hawk Console access to only highly trusted administrators and monitor for unauthorized credential access.

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
HawkApplication
Affected:>= 6.1.0, < 6.2.2
Operational Intelligence Hawk RedtailApplication
Affected:>= 7.0.0, < 7.2.1

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 TIBCO Hawk version
    Locate the TIBCO Hawk installation directory and check the version file or use the hawk -version command if available. Common paths include $TIBCO_HOME/hawk/version or check the product manifest.
    Affected if The installed version is 6.1.0 through 6.2.1 (for Tibco Hawk) or 7.0.0 through 7.2.0 (for Tibco Operational Intelligence Hawk Redtail)
  2. Verify Hawk Console is enabled
    Check the Hawk configuration files (typically hawk.xml or hawk.cfg in the hawk/etc or conf directory) for console-related settings. Look for console.enabled or similar configuration flags.
    Affected if Hawk Console feature is enabled in the configuration
  3. Confirm privileged user access exists
    Review the Hawk user configuration files to identify users with administrator or privileged roles. Check files such as users.xml, security.xml, or the underlying authentication repository configured for Hawk.
    Affected if There are privileged/administrative users configured with access to Hawk Console
  4. Check network exposure of Hawk Console
    Examine the Hawk Console binding configuration to determine if it listens on external network interfaces (0.0.0.0) versus localhost only. Check the console port setting in the Hawk configuration.
    Affected if Hawk Console is bound to accessible network interfaces and reachable from untrusted networks

The environment is affected if TIBCO Hawk version is 6.1.0-6.2.1 or Redtail version is 7.0.0-7.2.0 AND Hawk Console is enabled with privileged user access configured.

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 6.2.2 / 7.2.1 or later
Fixed in 6.2.27.2.1
Interim mitigation

Apply vendor patches for the affected versions. Until patches are applied, restrict Hawk Console access to only highly trusted administrators and monitor for unauthorized credential access.

Recommended fix High confidence

TIBCO Hawk 6.2.2 or later; TIBCO Operational Intelligence Hawk RedTail 7.2.1 or later

  1. Identify all instances running TIBCO Hawk versions 6.1.0 through 6.2.1
  2. Identify all instances running TIBCO Operational Intelligence Hawk RedTail versions 7.0.0 through 7.2.0
  3. Schedule a maintenance window for the upgrade process
  4. Back up current configuration files and deployment settings
  5. For TIBCO Hawk: upgrade to version 6.2.2 or later
  6. For TIBCO Operational Intelligence Hawk RedTail: upgrade to version 7.2.1 or later
  7. Verify the upgrade was successful by checking the Hawk Console version information
  8. Test that the Hawk Console functions normally after upgrade
Caveat Review TIBCO release notes for 6.2.2 and 7.2.1 for any compatibility or configuration changes that may affect your deployment

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

Fix this in Hawk 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 the upgrade done

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-41564 — 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-41564 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