dbcve.org
ConcertApplication · Ibm

CVE-2025-36154

MEDIUM · 6.2 CVSS v3.1 Published 2025-12-24
Fix available
A fix is available. Upgrade to 2.2.0 or later.
See remediation →
67/100
Remediation priority · Elevated
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 1.0.0 through 2.1.0 stores sensitive information in cleartext during recursive docker builds which could be obtained by a local user.

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 versions 1.0.0 through 2.1.0 has a cleartext storage vulnerability where sensitive information (likely credentials, secrets, or tokens used in the build process) is stored in cleartext on disk during recursive Docker builds. A local user with access to the system could potentially read this sensitive data from the Docker build artifacts or intermediate layers.

MitigationImplement encryption or secure handling for all sensitive data during Docker build processes. Remove or secure any cleartext sensitive data from Docker build contexts, build scripts, and intermediate layers. Consider using Docker secrets, buildkit caching with encryption, or external secret management.

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.2.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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/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 IBM Concert installation and version
    Run 'ibm-concert --version' or check the installed package version using your system's package manager (e.g., 'dpkg -l | grep concert', 'rpm -qa | grep concert', or 'brew list ibm-concert' depending on your OS)
    Affected if The installed version is >= 1.0.0 and < 2.2.0
  2. Locate Docker build context directories used by IBM Concert
    Search for Dockerfiles, build scripts, or build directories in common project locations such as the current working directory, ~/.concert/builds, or any directory configured in IBM Concert settings
    Affected if Docker build artifacts, Dockerfiles, or build scripts exist in the environment
  3. Inspect Docker build directories for cleartext sensitive data
    Examine the contents of identified Docker build directories and any scripts (e.g., Dockerfile, build.sh, *.dockerfile) for hardcoded credentials, API keys, tokens, or secrets using 'grep -r -E "(password|token|secret|key)" <build_directory>'
    Affected if Cleartext credentials, secrets, tokens, or keys are found in Docker build files or scripts
  4. Check Docker layer storage for exposed secrets
    If Docker build artifacts exist, inspect Docker layer history or build cache using 'docker history <image>' or 'docker build --progress=plain <path>' to observe whether sensitive data appears in build output or logs
    Affected if Sensitive data appears in Docker build output, layers, or intermediate container filesystems

You are affected if IBM Concert version 1.0.0 to less than 2.2.0 is installed and Docker builds are performed that store credentials, secrets, or tokens in cleartext within Dockerfiles, build scripts, or Docker layer cache.

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.2.0 or later
Fixed in 2.2.0
Interim mitigation

Implement encryption or secure handling for all sensitive data during Docker build processes. Remove or secure any cleartext sensitive data from Docker build contexts, build scripts, and intermediate layers. Consider using Docker secrets, buildkit caching with encryption, or external secret management.

Recommended fix High confidence

2.2.0

  1. Upgrade IBM Concert to version 2.2.0 or later to resolve the cleartext storage vulnerability
  2. After upgrading, verify that docker build processes no longer store sensitive information in cleartext
  3. Review release notes for version 2.2.0 to ensure all changes are compatible with your deployment
Caveat Review IBM Concert 2.2.0 release notes for any configuration or behavior changes that may affect your deployment

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

Fix this in Concert Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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