CyberSecBulletin
CVE-2025-42928NVD status: Deferred

SAP jConnect - SDK for ASE: Deserialization of Untrusted Data

Published Updated By the CyberSecBulletin desk

CVE-2025-42928 is a critical-severity deserialization of untrusted data vulnerability in SAP jConnect - SDK for ASE from SAP, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. Affected SAP jConnect - SDK for ASE versions: SYBASE_SOFTWARE_DEVELOPER_KIT 16.0.4; 16.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 9.82% chance of exploitation within 30 days, which is in the top 4.37% of all scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Check which version of SAP jConnect - SDK for ASE you run against the affected versions below, and install the vendor's latest release.

Affected products and versions

VendorProductAffected versionsFixed in
SAPSAP jConnect - SDK for ASESYBASE_SOFTWARE_DEVELOPER_KIT 16.0.4; 16.1Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
HighAdministrator-level access is required first.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (sap.com).

Official description

Under certain conditions, a high privileged user could exploit a deserialization vulnerability in SAP jConnect to launch remote code execution. The system may be vulnerable when specially crafted input is used to exploit the vulnerability resulting in high impact on confidentiality, integrity and availability of the system.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Deserialization of Untrusted Data

The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

How developers prevent this class of flaw

  • If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
  • When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
  • Explicitly define a final object() to prevent deserialization.

More Deserialization of Untrusted Data vulnerabilities (CWE-502)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Deserialization of Untrusted Data vulnerabilities

Spotted an error? Tell us.