Skip to main content

IBM CVE-2025-12708

| EUVDEUVD-2025-209008 MEDIUM
Use of Hard-coded Credentials (CWE-798)
2026-03-25 ibm GHSA-j796-6jhh-59m4
6.2
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Credential externalization
MITRE ATT&CK

2 techniques across 2 tactics: Persistence, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

While the CVSS score of 6.2 reflects moderate severity, the real-world risk requires careful contextualization using multiple signals. The CVSS vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) indicates low attack complexity with purely local attack vector, meaning only users with file system access can exploit this—significantly limiting the attack surface compared to network-based vulnerabilities. The absence of integrity or availability impact constrains the vulnerability's scope; an attacker gains unauthorized read access but cannot modify system data or cause denial of service. Critically, a patch is available from IBM, suggesting the vendor has already addressed this issue, which should reduce exploitation in patched environments. The vulnerability's real priority depends on environmental factors: systems running unpatched versions 1.0.0-2.2.0 in multi-tenant or untrusted-user environments face elevated risk, but fully-patched deployments or single-user/isolated systems face minimal risk. This is a 'patch-and-verify' priority rather than a critical emergency.

Exploit ScenarioDerived

A low-privileged local user on a system running unpatched IBM Concert (versions 1.0.0-2.2.0) reads the application's binary, configuration files, or source code and extracts the hard-coded credentials. Using these credentials, the attacker authenticates to Concert with elevated privileges, potentially gaining unauthorized access to sensitive data or administrative functions. Because the attack vector is local and complexity is low, an insider threat or attacker with shell access to the host system can trivially execute this exploitation without specialized tools.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 25, 2026

IBM Concert versions 1.0.0 through 2.2.0 contain hard-coded credentials accessible to local users, enabling unauthorized authentication bypass and potential privilege escalation. An attacker with local access can extract these credentials to gain unauthorized system access without requiring network connectivity or user interaction. This vulnerability is classified as moderate severity (CVSS 6.2) with high confidentiality impact but no direct integrity or availability impact.

RemediationAI

Immediately upgrade IBM Concert to version 2.3.0 or later, which contains the fix for hard-coded credentials (refer to vendor advisory at https://www.ibm.com/support/pages/node/7267105 for precise patching procedures). If immediate patching is not feasible, implement compensating controls: restrict local file system access to Concert installations using operating-system-level access controls (e.g., file permissions, SELinux, AppArmor) to limit exposure to local users; audit and rotate any credentials that may have been obtained from hard-coded sources; and monitor authentication logs for unauthorized access attempts. For environments where Concert must remain unpatched temporarily, isolate affected systems from untrusted users and conduct a thorough security review of any local accounts with potential access.

Affected VersionsENISA

Concert 1.0.0 ≤2.2.0

Affected Packages

euvd concert no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is rooted in CWE-798 (Use of Hard-Coded Credentials), a critical authentication control weakness where sensitive credentials are embedded directly in application code, configuration files, or binaries rather than being dynamically managed through secure credential stores. IBM Concert (cpe:2.3:a:ibm:concert:*:*:*:*:*:*:*:*) fails to implement secure credential management practices across versions 1.0.0 through 2.2.0. Hard-coded credentials are particularly dangerous because they cannot be rotated post-deployment, cannot be individualized per installation, and become permanent security liabilities if the code is decompiled or configuration files are inspected. This weakness directly undermines the authentication mechanism that should verify user identity before granting system access.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 6.2 MEDIUM
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

2
Patch released
Mar 25, 2026 - 20:17 nvd
Patch available
CVE Published
Mar 25, 2026 - 20:04 nvd
MEDIUM 6.2

DescriptionCVE.org

IBM Concert 1.0.0 through 2.2.0 contains hard-coded credentials that could be obtained by a local user.

Executive ViewAI

Why It Matters

Organizations using IBM Concert 1.0.0 through 2.2.0 should be aware of moderate risk from CVE-2025-12708, a hard-coded credentials vulnerability rated CVSS 6.2. Exploitation could allow attackers to execute code or inject malicious input. A patch is available and should be applied during regular vulnerability management.

Business Impact: Low
Compensating Controls

Apply vendor patch. If patching is delayed: restrict network access, enable MFA, monitor auth logs.

Threat Intelligence Overview

EPSS Score
0.0%
Top 99% exploitable
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
Low
Technical Impact
Partial

Priority Score

31
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +31
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy