CVE-2023-26219
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 · uneditedThe Hawk Console and Hawk Agent components of TIBCO Software Inc.'s TIBCO Hawk, TIBCO Hawk Distribution for TIBCO Silver Fabric, TIBCO Operational Intelligence Hawk RedTail, and TIBCO Runtime Agent contain a vulnerability that theoretically allows an attacker with access to the Hawk Console’s and Agent’s log to obtain credentials used to access associated EMS servers. Affected releases are TIBCO Software Inc.'s TIBCO Hawk: versions 6.2.2 and below, TIBCO Hawk Distribution for TIBCO Silver Fabric: versions 6.2.2 and below, TIBCO Operational Intelligence Hawk RedTail: versions 7.2.1 and below, and TIBCO Runtime Agent: versions 5.12.2 and below.
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 confidenceThe Hawk Console and Hawk Agent components contain a vulnerability where credentials used to access EMS servers are written in plaintext to log files. An attacker with access to these logs can obtain the exposed credentials and gain unauthorized access to associated EMS servers.
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< 6.2.3< 6.2.3< 7.2.2< 5.12.3CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Tibco Hawk product and versionLocate the Tibco Hawk installation directory and check the version file or use 'hawk version' command if available. Common locations include $TIBCO_HOME/hawk or check the product's manifest/version file.Affected if The installed version is lower than 6.2.3 for Tibco Hawk or Tibco Hawk Distribution For Silver Fabric, lower than 7.2.2 for Tibco Operational Intelligence Hawk Redtail, or lower than 5.12.3 for Tibco Runtime Agent.
-
Verify if Hawk credentials are configuredCheck the Hawk configuration files (such as hawk.cfg,hawk.conf, or associated deployment descriptors) for EMS server connection credentials. Look for entries containing EMS user credentials, passwords, or authentication tokens.Affected if EMS credentials are configured in Hawk configuration files - the vulnerability only affects environments where credentials are stored for accessing EMS servers.
-
Examine Hawk Console log files for plaintext credentialsLocate Hawk Console log files (typically in the logs directory under the Hawk installation). Search log files for strings containing 'password', 'credential', or EMS connection strings with embedded credentials using 'grep -i password' or similar search tools.Affected if Log files contain plaintext passwords, usernames, or credential strings used to authenticate to EMS servers.
-
Examine Hawk Agent log files for plaintext credentialsLocate Hawk Agent log files on all nodes where Hawk Agents are deployed. Search these logs for plaintext credentials, password patterns, or EMS connection strings that may include authentication details.Affected if Hawk Agent log files contain plaintext credentials used to access EMS servers.
The environment is affected if any Tibco Hawk product version is below the fixed versions AND credentials for EMS server access are present in Hawk Console or Hawk Agent log files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.12.36.2.37.2.2
Upgrade to patched versions of the affected TIBCO products. Additionally, rotate any credentials that may have been exposed in logs and review log access controls to limit who can access Hawk Console and Hawk Agent log files.
TIBCO Hawk 6.2.3+ | Hawk Distribution for TIBCO Silver Fabric 6.2.3+ | Operational Intelligence Hawk RedTail 7.2.2+ | Runtime Agent 5.12.3+
- Identify which TIBCO Hawk product(s) are deployed in your environment (Hawk, Hawk Distribution for TIBCO Silver Fabric, Operational Intelligence Hawk RedTail, or Runtime Agent)
- For TIBCO Hawk: upgrade to version 6.2.3 or later
- For TIBCO Hawk Distribution for TIBCO Silver Fabric: upgrade to version 6.2.3 or later
- For TIBCO Operational Intelligence Hawk RedTail: upgrade to version 7.2.2 or later
- For TIBCO Runtime Agent: upgrade to version 5.12.3 or later
- After upgrading, rotate any EMS server credentials that may have been exposed in logs, as a precautionary measure
- Review Hawk Console and Agent logs to confirm no unauthorized access has occurred using the exposed credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-26219 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-26219 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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