Security Verify GovernanceApplication · Ibm

CVE-2023-35019

HIGH · 8.8 CVSS v3.1 Published 2023-07-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
IBM Security Verify Governance, Identity Manager 10.0 could allow a remote authenticated attacker to execute arbitrary commands on the system by sending a specially crafted request. IBM X-Force ID: 257873.

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, Identity Manager 10.0 contains an authenticated command injection vulnerability. A remote attacker with valid credentials can send specially crafted requests to execute arbitrary operating system commands on the target system due to insufficient input validation.

MitigationApply the IBM security patch for CVE-2023-35019. If no patch is immediately available, restrict network access to the management interface to trusted IPs only and monitor for suspicious administrative activity.

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

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
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 checks

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

  1. Confirm IBM Security Verify Governance is installed
    Locate the IBM Security Verify Governance installation. Check for installation directories such as /opt/IBM/isvg, /opt/IBM/itim, or on Windows check Program Files for IBM folder. Alternatively, look for running processes with names containing 'itim', 'isig', or 's透verify'.
    Affected if IBM Security Verify Governance (or formerly Tivoli Identity Manager) is installed on the system
  2. Verify the installed version is 10.0
    Query the installed product version. This can typically be done through the IBM console under 'About' section, or by checking version files in the installation directory (such as VERSION.txt, build.info, or similar). Compare the version number against the affected range.
    Affected if The installed version is exactly 10.0
  3. Check if management interface is network-accessible
    Review firewall rules and network configuration to determine if the administrative console port (default HTTPS ports 443 or 9443) is exposed to untrusted or external networks. Use netstat or ss to list listening ports and their binding addresses.
    Affected if The management interface port is bound to 0.0.0.0 or is accessible from untrusted network segments
  4. Examine logs for suspicious command execution
    Review IBM Security Verify Governance application logs and system audit logs for unusual entries. Look for unexpected API calls, shell command invocations, or requests containing special characters that may indicate injection attempts. Check /opt/IBM/isvg/logs or the equivalent log directory.
    Affected if Logs show unexpected shell commands, unusual API calls, or signs of injection attempts

Your environment is affected if IBM Security Verify Governance version 10.0 is installed, the management interface is network-accessible, and either valid credentials exist or suspicious command execution is observed in logs.

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

Apply the IBM security patch for CVE-2023-35019. If no patch is immediately available, restrict network access to the management interface to trusted IPs only and monitor for suspicious administrative activity.

Fix this in Security Verify Governance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35019 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-35019 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