CVE-2023-42011
Ibm Sterling B2B Integrator 6.1 … 6.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NCVSS 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-42011 is a medium-severity Improper Restriction of Rendered UI Layers or Frames (CWE-1021) vulnerability in Ibm Sterling B2B Integrator. Its CVSS base score is 4.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Input Capture (T1056); ranked at the 13th 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
- 🇪🇺 ENISA EUVD: EUVD-2023-46470
Vulnerability Data
IBM Sterling B2B Integrator Standard Edition 6.1 and 6.2 does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain, which can lead to user confusion about which interface the user is interacting…
more
with. IBM X-Force ID: 265508.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
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.
Secure SDLC practices directly require implementing frame-ancestors / X-Frame-Options controls that prevent this weakness.
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.
Security testing can detect missing frame protections, but does not itself implement the control.
Training developers on web application security can make them aware of clickjacking and the need for X-Frame-Options or CSP frame-ancestors headers, but this is a specific technical implementation detail that requires deliberate coding, and not all developers receive this specialized training; the remainder is developers who lack the specific knowledge or who omit the protection despite knowing about it.
Secure coding practices directly require implementation of frame-busting headers or CSP frame-ancestors directives.
A.8.30 carries secure coding (8.28) and security testing (8.29) into the supplier contract, so clickjacking protections (X-Frame-Options, CSP frame-ancestors) are required of outsourced web development the same way those practices are; the effect is partial because it depends on supplier implementation rigour and the clause's ceiling on software weaknesses is partial.
A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw. Clickjacking does surface as CVEs in third-party components (e.g., CVE-2017-5697 firmware, CVE-2017-4015 DLP product), so A.8.8 finds that minority. The bulk of CWE-1021, however, is a first-party web application configuration/coding defect (missing X-Frame-Options / CSP frame-ancestors), which A.8.8's disclosure-based programme does not reach.
A.8.9's configuration templates and monitoring can enforce HTTP headers (X-Frame-Options, CSP frame-ancestors) that are the primary clickjacking mitigation, removing existing header-misconfiguration instances; however, code-level frame-busting logic and applications with context-dependent framing requirements are outside configuration management's reach, leaving a nameable remainder.