dbcve.org
Security Verify GovernanceApplication · Ibm

CVE-2022-22466

CRITICAL · 9.8 CVSS v3.1 Published 2023-10-23
Fix available
A fix is available. Upgrade to 10.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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
IBM Security Verify Governance 10.0 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. IBM X-Force ID: 225222.

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

IBM Security Verify Governance 10.0 contains hard-coded credentials (passwords or cryptographic keys) embedded in the product. These credentials are used for three distinct purposes: inbound authentication to the system itself, outbound communication to external components, and encryption of internal data. An attacker with knowledge of these credentials could authenticate as legitimate users, intercept or manipulate external communications, or decrypt sensitive internal data.

MitigationIdentify and replace all hard-coded credentials with properly managed secrets using a secrets management solution (e.g., HashiCorp Vault, IBM Cloud Secrets Manager, or environment variables). Immediately rotate any credentials that may have been exposed. Test all authentication, communication, and encryption functions after remediation.

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
Security Verify GovernanceApplication
Affected:>= 10.0, < 10.0.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of IBM Security Verify Governance
    Use the product's version check mechanism (typically via admin console, command line, or version file) to determine the exact installed version
    Affected if The installed version is 10.0.0 or 10.0.1 (falls in the range >= 10.0 and < 10.0.2)
  2. Search for hard-coded passwords in configuration files
    Inspect configuration directories and files (such as XML, properties, or config files in the installation directory) for embedded password strings used for authentication
    Affected if Plaintext or encoded passwords are found hard-coded in configuration files for inbound authentication or user accounts
  3. Search for hard-coded credentials used for outbound communication
    Review configuration files and connection settings that define external system connections (databases, LDAP, APIs, or other integrations) for embedded credentials
    Affected if Credentials used to connect to external components are found hard-coded rather than managed through secrets management
  4. Search for hard-coded cryptographic keys
    Inspect application files, key stores, or configuration for embedded encryption keys used for internal data protection
    Affected if Cryptographic keys or secrets used for encrypting internal data are found hard-coded in the product
  5. Audit authentication and encryption configurations
    Review the product's security configuration settings, particularly authentication mechanisms and data encryption settings, to identify any using built-in static credentials
    Affected if Authentication modules, encryption settings, or security configurations rely on built-in credentials that cannot be changed or are not managed externally

A user is affected if their IBM Security Verify Governance installation is version 10.0 or 10.0.1 AND contains hard-coded credentials (passwords or cryptographic keys) embedded in configuration files, authentication modules, or encryption settings.

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 10.0.2 or later
Fixed in 10.0.2
Interim mitigation

Identify and replace all hard-coded credentials with properly managed secrets using a secrets management solution (e.g., HashiCorp Vault, IBM Cloud Secrets Manager, or environment variables). Immediately rotate any credentials that may have been exposed. Test all authentication, communication, and encryption functions after remediation.

Recommended fix High confidence

10.0.2

  1. Backup the current IBM Security Verify Governance installation and configuration
  2. Review IBM documentation and release notes for version 10.0.2 for any specific upgrade requirements
  3. Upgrade IBM Security Verify Governance from the current 10.0.x version to version 10.0.2
  4. After upgrade, verify that all services are running correctly
  5. Change any default or hard-coded credentials as part of standard hardening procedures following the upgrade

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

Fix this in Security Verify Governance Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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