dbcve.org
ConcertApplication · Ibm

CVE-2025-33090

HIGH · 7.5 CVSS v3.1 Published 2025-08-18
Fix available
A fix is available. Upgrade to 2.0.0 or later.
See remediation →
84/100
Remediation priority · High
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 Concert Software 1.0.0 through 1.1.0 could allow a remote attacker to cause a denial of service using a specially crafted regular expression that would cause excessive resource consumption.

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

IBM Concert Software versions 1.0.0 through 1.1.0 is vulnerable to a Regular Expression Denial of Service (ReDoS) attack. A remote unauthenticated attacker can submit specially crafted regular expressions that trigger excessive backtracking, causing high CPU consumption and service disruption.

MitigationUpdate IBM Concert Software to a version beyond 1.1.0 containing the vendor patch. If immediate patching is not possible, implement request rate limiting and input validation on endpoints that process user-supplied regex patterns.

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
ConcertApplication
Affected:>= 1.0.0, < 2.0.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 if IBM Concert is installed
    Check your system for IBM Concert Software installation. Common locations include /opt/ibm/concert, /usr/local/ibm/concert, or review your software inventory/packaging system for 'ibm-concert' or 'IBM Concert'.
    Affected if IBM Concert Software is installed on the system
  2. Determine the installed version
    Run 'ibm-concert --version' or check the version file in the installation directory (commonly version.txt, VERSION, or package.json in the install root). Compare the version number to the affected range: >= 1.0.0 and < 2.0.0.
    Affected if The installed version falls within 1.0.0 to 1.1.0 inclusive
  3. Identify regex processing endpoints
    Review your IBM Concert configuration and API documentation to locate endpoints or features that accept and process user-supplied regular expressions. Check configuration files for regex-related settings or modules (look for 'regex', 'pattern', 'regexp' in config files).
    Affected if The IBM Concert instance exposes functionality that processes user-supplied regex patterns from unauthenticated or authenticated users
  4. Check network exposure of regex features
    Review network access controls and firewall rules to determine if the identified regex processing endpoints are exposed to unauthenticated network access. Check if the service is bound to non-localhost interfaces.
    Affected if Regex processing endpoints are accessible to unauthenticated remote attackers without authentication requirements

You are affected if IBM Concert version 1.0.0 through 1.1.0 is installed AND your deployment exposes functionality that processes user-supplied regular expressions to remote attackers.

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

Update IBM Concert Software to a version beyond 1.1.0 containing the vendor patch. If immediate patching is not possible, implement request rate limiting and input validation on endpoints that process user-supplied regex patterns.

Recommended fix Moderate confidence

IBM Concert Software 2.0.0 or later

  1. Check IBM's official security bulletin at www.ibm.com for CVE-2025-33090 to confirm the exact fixed version and any special upgrade instructions.
  2. If available, review upgrade documentation for IBM Concert from version 1.x to the fixed release to understand any prerequisites.
  3. Plan upgrade during a maintenance window as this is a denial of service vulnerability.
  4. Backup current configuration and data before performing the upgrade.
  5. Upgrade IBM Concert Software to version 2.0.0 or later which contains the fix for the ReDoS vulnerability.
  6. After upgrade, verify the service starts correctly and test that the application is functional.
Caveat Review release notes for version 2.0.0 for any breaking changes or migration requirements from version 1.x

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

Fix this in Concert Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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