dbcve.org
Jscape MftApplication · Redwood

CVE-2023-4528

HIGH · 7.2 CVSS v3.1 Published 2023-09-07
Fix available
A fix is available. Upgrade to 2023.1.9 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Unsafe deserialization in JSCAPE MFT Server versions prior to 2023.1.9 (Windows, Linux, and MacOS) permits an attacker to run arbitrary Java code (including OS commands) via its management interface

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 · high confidence

JSCAPE MFT Server versions before 2023.1.9 contain an unsafe deserialization vulnerability in its management interface that allows authenticated or unauthenticated attackers to deserialize untrusted data without proper validation, leading to arbitrary Java code execution and OS command injection.

MitigationUpgrade JSCAPE MFT Server to version 2023.1.9 or later. Until upgrade is possible, restrict network access to the management interface using firewall rules or VPN access controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jscape MftApplication
Affected:< 2023.1.9

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed JSCAPE MFT Server version
    Locate the JSCAPE installation directory and check the version file or banner. Common locations include the /version/ endpoint on the management web interface, a version.txt file in the installation folder, or the server startup logs.
    Affected if The displayed version number is less than 2023.1.9 (for example, 2023.1.8, 2023.1.0, or any 2022.x release).
  2. Determine if management interface is network-exposed
    Check if the JSCAPE management web interface port (typically 8080, 8443, or 9090) is bound to a public or untrusted network interface, or is accessible from outside the local network. Use 'netstat -an' or 'ss -tlnp' to review listening ports and their binding addresses.
    Affected if The management interface listens on 0.0.0.0 or is reachable from untrusted networks without VPN or firewall filtering.
  3. Verify management interface authentication status
    Attempt to access the management interface login page from an untrusted location, or review the server configuration file (typically admin.xml, server.xml, or the admin settings in the JSCAPE configuration directory) to confirm whether authentication enforcement is enabled.
    Affected if The management interface allows unauthenticated access or authentication is disabled in the configuration.
  4. Inspect for deserialization-related configurations
    Review JSCAPE configuration files (particularly in the /conf or /config directory) for any settings related to Java deserialization, object streaming, or custom serializer configurations. Check if any non-default settings allow untrusted data handling.
    Affected if Deserialization is enabled for untrusted input sources or custom serialization handlers are configured without validation.

A user is affected if their installed JSCAPE MFT Server version is below 2023.1.9 and the management interface is network-accessible without proper access controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2023.1.9 or later
Fixed in 2023.1.9
Interim mitigation

Upgrade JSCAPE MFT Server to version 2023.1.9 or later. Until upgrade is possible, restrict network access to the management interface using firewall rules or VPN access controls.

Recommended fix High confidence

2023.1.9

  1. 1. Back up the current JSCAPE MFT Server configuration and data directory
  2. 2. Download JSCAPE MFT Server version 2023.1.9 or later from the vendor's official download portal
  3. 3. Stop the JSCAPE MFT Server service
  4. 4. Install the upgrade following the vendor's documented upgrade procedure
  5. 5. Restart the JSCAPE MFT Server service
  6. 6. Verify the server is running and accessible via the management interface

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jscape Mft Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4528 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4528 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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