Cyber Resilience

CVE-2024-35112

XSS in Ibm Control Center 6.2.1.0 … 6.3.1.0

Published
25 January 2025
Modified
04 March 2025
Patch / advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0030 22th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2024-35112 is a medium-severity Basic XSS (CWE-80) vulnerability in Ibm Control Center. Its CVSS base score is 5.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Control Center 6.2.1 and 6.3.1 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
T1592.002 Software Reconnaissance
Adversaries may gather information about the victim's host software that can be used during targeting.
T1082 System Information Discovery Discovery
An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture.
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
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-2024-35111Same product: Ibm Control Center
CVE-2024-35114Same product: Ibm Control Center
CVE-2023-43052Same product: Ibm Control Center
CVE-2024-35113Same product: Ibm Control Center
CVE-2025-36328Same vendor: Ibm
CVE-2024-49798Same vendor: Ibm
CVE-2026-1248Same vendor: Ibm
CVE-2024-49818Same vendor: Ibm
CVE-2023-49878Same vendor: Ibm
CVE-2024-45659Same vendor: Ibm

Affected Assets

ibm
control center
6.2.1.0, 6.3.1.0

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
  • V1.2.1
  • V1.3.1
  • V1.3.3

Mitigating Controls (NIST 800-53 r5) AI

si-11 directly requires error messages to avoid revealing exploitable information about the system or its data.

Developer testing and evaluation can discover missing or incorrect neutralization of script tags through targeted XSS test cases.

Input validation explicitly requires checking and neutralizing untrusted web inputs containing script-related characters before they reach a downstream renderer.

Secure engineering principles include mandatory output encoding and neutralization of HTML metacharacters to stop injection at the source.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require output encoding and input validation that prevent basic XSS.

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

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards explicitly forbid exposing sensitive data in errors.

finds

Security testing in development catches unneutralized script tags before release.

A.8.15 Logging partial match
degrades

Logging policy can require suppression of sensitive data in error messages.

prevents

Secure SDLC mandates input validation and output encoding that directly prevent basic XSS.

prevents

Application security requirements explicitly call for neutralization of script-related HTML tags.

prevents

Secure architecture principles include proper exception handling.

References