Security Resilience

CVE-2023-40682

Info Disclosure in Ibm App Connect Enterprise 12.0.1.0 – 12.0.9.0

Published
13 October 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 4.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0019 9th percentile
Risk Priority 34 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-40682 is a medium-severity Insertion of Sensitive Information into Log File (CWE-532) vulnerability in Ibm App Connect Enterprise. Its CVSS base score is 4.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Local Accounts (T1078.003); ranked at the 9th 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 App Connect Enterprise 12.0.1.0 through 12.0.8.0 contains an unspecified vulnerability that could allow a local privileged user to obtain sensitive information from API logs. IBM X-Force ID: 263833.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1078.003 Local Accounts Stealth
Adversaries may obtain and abuse credentials of a local account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
T1552.003 Shell History Credential Access
Adversaries may search the command history on compromised systems for insecurely stored credentials.
T1552.007 Container API Credential Access
Adversaries may gather credentials via APIs within a containers environment.
T1589.001 Credentials Reconnaissance
Adversaries may gather credentials 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-2026-12947Same product: Ibm App Connect Enterprise
CVE-2026-5515Same product: Ibm App Connect Enterprise
CVE-2024-22317Same product: Ibm App Connect Enterprise
CVE-2024-31893Same product: Ibm App Connect Enterprise
CVE-2024-31894Same product: Ibm App Connect Enterprise
CVE-2024-31895Same product: Ibm App Connect Enterprise
CVE-2024-28761Same product: Ibm App Connect Enterprise
CVE-2023-50301Same vendor: Ibm
CVE-2025-36361Same product: Ibm App Connect Enterprise
CVE-2025-1998Same vendor: Ibm

Affected Assets

ibm
app connect enterprise
12.0.1.0 — 12.0.9.0

Mitigating Controls

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

Procedures mandate excluding sensitive data from logs to prevent unauthorized exposure via audit records.

addresses: CWE-532

Identifies insertion of sensitive data into logs, allowing detection of unauthorized disclosure.

addresses: CWE-532

Cross-organizational coordination enables agreement on what data to include in audit logs, directly reducing insertion of sensitive information.

addresses: CWE-532

Identifying logging as a data action allows prevention of sensitive information being inserted into log files.

addresses: CWE-532

The process of identifying and eradicating spilled information applies directly to sensitive data inserted into log files.

addresses: CWE-532

Specific processing rules for sensitive PII categories commonly include restrictions on logging, making insertion of such data into log files less likely.

addresses: CWE-532

PIAs detect planned or existing logging of PII and require removal or protection, preventing insertion of sensitive information into logs.

addresses: CWE-532

Limits insertion of sensitive operational details into logs by treating such data as key information requiring protection.

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 prohibit writing sensitive data to logs; eliminating the weakness satisfies only one narrow slice of the control.

PR.PS-04 partial match
blocks

Log generation configuration can and should exclude sensitive data, but the control statement focuses on availability rather than content filtering.

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.

blocks

A.5.15 mandates that access control rules be defined and implemented on assets including log files (it explicitly references logging under 8.15 and requires access rights and restrictions to be mapped to entities), so a well-implemented policy restricts who can read the log and blocks the exploitation; the actual enforcement, however, is performed by the access control implementation (A.8.3 and related), not by A.5.15 itself, which sits one step removed as the policy that requires the blocking to be set up.

prevents

A.8.28 mandates secure coding practices that include guidance on what not to log (sensitive data is exactly the kind of 'common and historical coding practice' the clause names), but the mechanism is human practice — developers must know what counts as sensitive, redact it, and apply that consistently across error paths and third-party libraries. This is the same practice-not-mechanism reading that graded A.8.28 -> CWE-79 and A.8.28 -> CWE-502 at `partial`, and the clause carries a declared ceiling of `partial` on this verb for code-level defects.

finds

A.8.29's SOURCE reach (SAST, code review) catches the bulk of CWE-532 instances where sensitive data is passed directly to logging calls, and RUNTIME reach (penetration testing) can surface sensitive data in accessible logs; the remainder is bounded and nameable — cases where sensitivity is context-dependent and not flagged by configured rules, and indirect logging patterns (e.g., logging entire objects whose toString() exposes sensitive fields) that SAST rules miss.

blocks

A.8.3 restricts who may access information that exists, but CWE-532 is about the product writing sensitive information into a log file in the first place; access restriction does not stop the log entry from being created or read by an attacker who reaches the log through a different path.

prevents

A.8.30 carries secure coding practices (8.28) into outsourced work via contract, and secure coding guidance typically addresses what should not be logged, so a faithful implementation reduces instances of CWE-532 in delivered code; the ceiling is `partial` because the effect depends on the rigour of the contracted practice and the clause's own ceiling on this verb is `partial` (per the CWE-134 anchor).

References