CVE-2025-42933: CWE-522: Insufficiently Protected Credentials in SAP_SE SAP Business One (SLD)
When a user logs in via SAP Business One native client, the SLD backend service fails to enforce proper encryption of certain APIs. This leads to exposure of sensitive credentials within http response body. As a result, it has a high impact on the confidentiality, integrity, and availability of the application.
AI Analysis
Technical Summary
CVE-2025-42933 is a high-severity vulnerability affecting SAP Business One (SLD) versions B1_ON_HANA 10.0 and SAP-M-BO 10.0. The vulnerability arises because the System Landscape Directory (SLD) backend service fails to enforce proper encryption on certain APIs when users log in via the SAP Business One native client. Specifically, sensitive credentials are exposed within the HTTP response body in plaintext or insufficiently protected form. This exposure violates secure handling of credentials (CWE-522: Insufficiently Protected Credentials), leading to a significant risk of credential compromise. An attacker with network access and at least limited privileges (PR:L) can intercept these responses over the network (AV:N) without requiring user interaction (UI:N). The vulnerability impacts confidentiality, integrity, and availability of the SAP Business One application, as attackers could leverage stolen credentials to escalate privileges, manipulate business data, or disrupt operations. The CVSS v3.1 base score is 8.8, reflecting the ease of exploitation and the critical impact on core security properties. No known exploits are currently reported in the wild, but the vulnerability's nature and the widespread use of SAP Business One in enterprise environments make it a significant concern. No patches have been linked yet, indicating that organizations must prioritize mitigation and monitoring until an official fix is released.
Potential Impact
For European organizations, this vulnerability poses a critical risk due to the widespread adoption of SAP Business One in small and medium enterprises (SMEs) and larger corporations across various sectors including manufacturing, retail, and services. Exposure of credentials can lead to unauthorized access to sensitive business data, financial information, and operational controls, potentially resulting in data breaches, financial fraud, and operational disruptions. Given the GDPR regulatory environment in Europe, a breach involving personal or sensitive data could lead to substantial fines and reputational damage. The vulnerability also threatens the integrity of business processes managed through SAP Business One, which could have cascading effects on supply chains and customer relations. Additionally, availability impacts could disrupt business continuity, especially if attackers leverage compromised credentials to deploy ransomware or other disruptive malware. The lack of user interaction requirement and network-level exploitability increase the risk of automated attacks and lateral movement within corporate networks.
Mitigation Recommendations
1. Immediate network-level controls: Restrict access to SAP Business One SLD services to trusted internal networks and VPNs only, using firewall rules and network segmentation to minimize exposure. 2. Enforce encryption: Where possible, configure SAP Business One and related infrastructure to enforce TLS encryption on all API communications, including internal service calls, to prevent credential interception. 3. Monitor network traffic: Deploy intrusion detection/prevention systems (IDS/IPS) and network monitoring tools to detect anomalous access patterns or suspicious API responses that may indicate exploitation attempts. 4. Credential hygiene: Rotate all credentials associated with SAP Business One SLD services and enforce strong password policies and multi-factor authentication (MFA) for all users with access. 5. Vendor engagement: Maintain close contact with SAP for timely receipt of patches or hotfixes addressing this vulnerability, and plan for rapid deployment once available. 6. Application-level logging and alerting: Enable detailed logging of authentication events and API access to facilitate forensic analysis and early detection of compromise. 7. User awareness: Educate users about the risks of credential compromise and encourage reporting of suspicious activity. These steps go beyond generic advice by focusing on network isolation, encryption enforcement, and proactive monitoring tailored to the specific vulnerability context.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Belgium, Sweden, Poland, Austria
CVE-2025-42933: CWE-522: Insufficiently Protected Credentials in SAP_SE SAP Business One (SLD)
Description
When a user logs in via SAP Business One native client, the SLD backend service fails to enforce proper encryption of certain APIs. This leads to exposure of sensitive credentials within http response body. As a result, it has a high impact on the confidentiality, integrity, and availability of the application.
AI-Powered Analysis
Technical Analysis
CVE-2025-42933 is a high-severity vulnerability affecting SAP Business One (SLD) versions B1_ON_HANA 10.0 and SAP-M-BO 10.0. The vulnerability arises because the System Landscape Directory (SLD) backend service fails to enforce proper encryption on certain APIs when users log in via the SAP Business One native client. Specifically, sensitive credentials are exposed within the HTTP response body in plaintext or insufficiently protected form. This exposure violates secure handling of credentials (CWE-522: Insufficiently Protected Credentials), leading to a significant risk of credential compromise. An attacker with network access and at least limited privileges (PR:L) can intercept these responses over the network (AV:N) without requiring user interaction (UI:N). The vulnerability impacts confidentiality, integrity, and availability of the SAP Business One application, as attackers could leverage stolen credentials to escalate privileges, manipulate business data, or disrupt operations. The CVSS v3.1 base score is 8.8, reflecting the ease of exploitation and the critical impact on core security properties. No known exploits are currently reported in the wild, but the vulnerability's nature and the widespread use of SAP Business One in enterprise environments make it a significant concern. No patches have been linked yet, indicating that organizations must prioritize mitigation and monitoring until an official fix is released.
Potential Impact
For European organizations, this vulnerability poses a critical risk due to the widespread adoption of SAP Business One in small and medium enterprises (SMEs) and larger corporations across various sectors including manufacturing, retail, and services. Exposure of credentials can lead to unauthorized access to sensitive business data, financial information, and operational controls, potentially resulting in data breaches, financial fraud, and operational disruptions. Given the GDPR regulatory environment in Europe, a breach involving personal or sensitive data could lead to substantial fines and reputational damage. The vulnerability also threatens the integrity of business processes managed through SAP Business One, which could have cascading effects on supply chains and customer relations. Additionally, availability impacts could disrupt business continuity, especially if attackers leverage compromised credentials to deploy ransomware or other disruptive malware. The lack of user interaction requirement and network-level exploitability increase the risk of automated attacks and lateral movement within corporate networks.
Mitigation Recommendations
1. Immediate network-level controls: Restrict access to SAP Business One SLD services to trusted internal networks and VPNs only, using firewall rules and network segmentation to minimize exposure. 2. Enforce encryption: Where possible, configure SAP Business One and related infrastructure to enforce TLS encryption on all API communications, including internal service calls, to prevent credential interception. 3. Monitor network traffic: Deploy intrusion detection/prevention systems (IDS/IPS) and network monitoring tools to detect anomalous access patterns or suspicious API responses that may indicate exploitation attempts. 4. Credential hygiene: Rotate all credentials associated with SAP Business One SLD services and enforce strong password policies and multi-factor authentication (MFA) for all users with access. 5. Vendor engagement: Maintain close contact with SAP for timely receipt of patches or hotfixes addressing this vulnerability, and plan for rapid deployment once available. 6. Application-level logging and alerting: Enable detailed logging of authentication events and API access to facilitate forensic analysis and early detection of compromise. 7. User awareness: Educate users about the risks of credential compromise and encourage reporting of suspicious activity. These steps go beyond generic advice by focusing on network isolation, encryption enforcement, and proactive monitoring tailored to the specific vulnerability context.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- sap
- Date Reserved
- 2025-04-16T13:25:34.581Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68bf8dfad5a2966cfc858174
Added to database: 9/9/2025, 2:16:26 AM
Last enriched: 9/9/2025, 2:31:41 AM
Last updated: 9/9/2025, 4:09:51 AM
Views: 5
Related Threats
CVE-2025-10123: Command Injection in D-Link DIR-823X
MediumCVE-2025-10122: SQL Injection in Maccms10
MediumCVE-2025-42958: CWE-250: Execution with Unnecessary Privileges in SAP_SE SAP NetWeaver
CriticalCVE-2025-42944: CWE-502: Deserialization of Untrusted Data in SAP_SE SAP Netweaver (RMI-P4)
CriticalCVE-2025-42938: CWE-79: Improper Neutralization of Input During Web Page Generation in SAP_SE SAP NetWeaver ABAP Platform
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.