CVE-2025-1348 is a medium-severity vulnerability affecting IBM Sterling B2B Integrator and IBM Sterling File Gateway versions 6.0.0.0 through 6.1.2.6 and 6.2.0.0 through 6.2.0.4. The issue arises from improper caching policies implemented in the web interface of these products, which allow sensitive information to be exposed through the user's web browser cache. Specifically, the affected software does not set appropriate cache-control headers or other mechanisms to prevent sensitive data from being stored in the browser cache. As a result, a local attacker with access to the affected user's machine could retrieve sensitive information by inspecting the browser cache contents. The vulnerability is classified under CWE-525 (Information Exposure Through Browser Caching). The CVSS v3.1 base score is 4.0, reflecting a low attack vector (local access required), low complexity, no privileges required, no user interaction needed, and limited impact confined to confidentiality without affecting integrity or availability. There are no known exploits in the wild at the time of publication, and no official patches have been linked yet. The vulnerability primarily affects environments where IBM Sterling B2B Integrator or File Gateway is used, which are enterprise-grade solutions for business-to-business file transfer and integration workflows. Given the nature of the vulnerability, the risk is mainly to confidentiality of sensitive data cached in the browser, which could include business documents, credentials, or other proprietary information displayed via the web interface. The attack requires local access to the victim's machine, making remote exploitation infeasible without prior compromise. This vulnerability highlights the importance of secure web application caching policies, especially for enterprise software handling sensitive transactions.

For European organizations, the impact of CVE-2025-1348 is primarily the potential exposure of sensitive business information through local access to cached browser data. Organizations using IBM Sterling B2B Integrator or File Gateway for critical B2B transactions could risk leakage of confidential documents, transaction details, or authentication tokens if an attacker gains local access to a user's workstation. This could lead to intellectual property theft, competitive disadvantage, or regulatory compliance issues, especially under GDPR where unauthorized data exposure must be reported. However, since the vulnerability requires local access and does not allow remote exploitation, the risk is somewhat mitigated by existing endpoint security controls. The integrity and availability of the systems are not affected, so operational disruption is unlikely. The threat is more significant in environments where shared or less-secure workstations are used, or where insider threats exist. European companies in sectors such as manufacturing, logistics, finance, and telecommunications that rely on IBM Sterling products for secure file exchange with partners may be particularly concerned about confidentiality breaches. Additionally, organizations with strict data protection requirements must ensure that browser caching does not inadvertently expose sensitive data to unauthorized local users.

To mitigate CVE-2025-1348, European organizations should implement the following specific measures: 1) Immediately review and restrict local access to workstations of users who interact with IBM Sterling B2B Integrator/File Gateway web interfaces to trusted personnel only. 2) Enforce endpoint security policies that prevent unauthorized users from accessing browser cache files, including using encrypted user profiles and disk encryption. 3) Configure browsers used to access IBM Sterling interfaces to disable or limit caching of sensitive pages, for example by using private/incognito modes or browser policies that disable caching for specific URLs. 4) Monitor and audit local access logs and user activity on systems running the affected software to detect potential insider threats or unauthorized access. 5) Apply any forthcoming patches or updates from IBM as soon as they become available to address the caching policy issue at the application level. 6) Consider deploying web application firewalls or reverse proxies that can inject appropriate cache-control headers if the application cannot be immediately updated. 7) Educate users about the risks of leaving sensitive sessions open on shared or public machines. These steps go beyond generic advice by focusing on local access controls, browser configuration, and compensating controls until a patch is released.