CVE-2025-42933
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWhen 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe SLD (System Landscape Directory) backend service in SAP Business One fails to enforce encryption on certain APIs during native client login, allowing sensitive credentials to be transmitted in plaintext within HTTP response bodies.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if SLD service is deployedCheck the SAP Business One system for presence of System Landscape Directory (SLD) service component. Consult SAP B1 administration console or system configuration to confirm SLD is enabled.Affected if SLD backend service is installed and active in the environment
-
Verify SLD encryption configurationAccess the SLD configuration settings or SAP B1 Server Tools to inspect whether TLS/SSL encryption is enabled for the SLD backend service. Look for encryption-related parameters in the SLD configuration files or administration interface.Affected if TLS/SSL encryption is not enabled or is set to optional/disabled for the SLD service
-
Inspect native client login API endpointsReview the SLD API configuration for endpoints handling native client authentication. Check whether these specific APIs enforce HTTPS or require encryption before accepting credentials.Affected if Native client login APIs do not require encrypted connections and accept plaintext transmission
-
Capture test login to observe credential transmissionIf permitted by policy, perform a test native client login while monitoring network traffic. Inspect HTTP request/response bodies to determine if credentials are transmitted in plaintext.Affected if Credentials are observed in plaintext within HTTP request or response bodies during login flow
-
Check SLD server certificate configurationVerify on the SLD server whether a valid TLS certificate is configured and whether the service is bound to an HTTPS port. Confirm that the server rejects non-encrypted connections.Affected if No valid TLS certificate is configured or the service accepts both encrypted and unencrypted connections
The environment is affected if the SLD backend service is running without enforced TLS/SSL encryption and the native client login APIs allow plaintext credential transmission.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataEnable and enforce TLS/SSL encryption on the SLD backend service and ensure all API communications require proper encryption before authentication credentials are transmitted.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-42933 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-42933 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data