Security Resilience

CVE-2023-27860

Info Disclosure in Ibm Maximo Asset Management 7.6.1.2 … 7.6.1.3

Published
27 April 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0053 45th percentile
Risk Priority 45 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-27860 is a medium-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability in Ibm Maximo Asset Management. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Domain Accounts (T1078.002); ranked at the 45th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Maximo Asset Management 7.6.1.2 and 7.6.1.3 could disclose sensitive information in an error message. This information could be used in further attacks against the system. IBM X-Force ID: 249207.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1078.002 Domain Accounts Stealth
Adversaries may obtain and abuse credentials of a domain account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
T1589.001 Credentials Reconnaissance
Adversaries may gather credentials that can be used during targeting.
T1589.003 Employee Names Reconnaissance
Adversaries may gather employee names that can be used during targeting.
T1592 Gather Victim Host Information Reconnaissance
Adversaries may gather information about the victim's hosts that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-2987Same product: Ibm Maximo Asset Management
CVE-2025-2986Same product: Ibm Maximo Asset Management
CVE-2023-27864Same product: Ibm Maximo Asset Management
CVE-2024-45088Same product: Ibm Maximo Asset Management
CVE-2024-45652Same product: Ibm Maximo Asset Management
CVE-2024-52893Same vendor: Ibm
CVE-2024-51460Same vendor: Ibm
CVE-2024-37524Same vendor: Ibm
CVE-2025-36328Same vendor: Ibm
CVE-2024-28765Same vendor: Ibm

Affected Assets

ibm
maximo asset management
7.6.1.2, 7.6.1.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V16.5.1

Likely Mitigating Controls

Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-209

Detects error messages that leak sensitive information as evidence of disclosure.

addresses: CWE-209

The control directly mitigates generation of error messages containing sensitive authentication details by requiring obscured feedback instead of verbose responses.

addresses: CWE-209

Misdirection allows generation of misleading error messages that withhold or falsify sensitive details.

addresses: CWE-209

Explicitly requires error messages to avoid including sensitive or exploitable details while still supporting corrective action.

addresses: CWE-209

Validation ensures error messages contain only expected, non-sensitive content and blocks leakage via verbose errors.

addresses: CWE-209

Fail-safe procedures can be defined to suppress or sanitize error output, reducing generation of messages that contain sensitive information.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require sanitized error handling to prevent sensitive data disclosure.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing can detect error messages that leak sensitive information.

prevents

Training makes developers aware that error messages must not leak sensitive information and that exception output should be sanitized, which prevents a minority of instances; the remainder is the same fallible-developer problem that caps A.8.28 against code-level defects like XSS.

prevents

Secure coding standards explicitly forbid exposing sensitive data in errors.

prevents

A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-209 is a regular software CWE that secure coding addresses, but the clause's reach depends on supplier implementation and error-message hygiene is one slice of what secure coding covers, with externally-generated error messages outside the developer's direct control.

removes

A.8.5 guidance items (a) and (c) specifically address error messages during the log-on procedure — not displaying sensitive information until log-on completes, and not providing help messages that would aid an unauthorized user (e.g., not indicating which part of the data is correct or incorrect). This removes a narrow subset of CWE-209 (log-on error message leaks), but the vast majority of CWE-209 instances — database errors, file processing errors, configuration errors, and general application error handling — are outside A.8.5's scope.

removes

A.8.9's templates and configuration enforcement can remove configuration-level instances of CWE-209 (e.g., disabling verbose error pages, suppressing debug output, setting generic error responses), but cannot reach the majority of instances where application code explicitly constructs error messages containing sensitive data — those require code changes the clause does not perform.

References