CVE-2023-42011: IBM Sterling B2B Integrator Standard Edition tapjacking

Published Jun 25, 2024
·
Updated

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 with. IBM X-Force ID: 265508.

Other sources

IBM Sterling B2B Integrator Standard Edition 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 with.

IBM

Affected Software

4 affected components
IBM Sterling B2B Integrator<=6.2
IBM Sterling B2B Integrator<=6.1
IBM Sterling B2B Integrator=6.1
IBM Sterling B2B Integrator=6.2

Event History

Jun 25, 2024
CVE Published
via IBM·12:00 AM
Jun 27, 2024
CVE Published
via MITRE·05:39 PM
Data Sourced
via MITRE·05:39 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2023-42011?

CVE-2023-42011 has been assigned a critical severity rating due to the potential for user confusion and misinteraction with UI layers.

2

How do I fix CVE-2023-42011?

To fix CVE-2023-42011, upgrade IBM Sterling B2B Integrator to a version that includes the necessary security patches.

3

Which versions of IBM Sterling B2B Integrator are affected by CVE-2023-42011?

CVE-2023-42011 affects IBM Sterling B2B Integrator versions 6.1 and 6.2.

4

What are the risks associated with CVE-2023-42011?

The risks of CVE-2023-42011 include user interaction with incorrect application interfaces, leading to potential data exposure or security breaches.

5

Is there a workaround for CVE-2023-42011?

Currently, there is no documented workaround for CVE-2023-42011, and upgrading is the recommended approach.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203