dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-43713

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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
ASNA Assist and ASNA Registrar before 2025-03-31 allow deserialization attacks against .NET remoting. These are Windows system services that support license key management and deprecated Windows network authentication. The services are implemented with .NET remoting and can be exploited via well-known deserialization techniques inherent in the technology. Because the services run with SYSTEM-level rights, exploits can be crafted to achieve escalation of privilege and arbitrary code execution. This affects DataGate for SQL Server 17.0.36.0 and 16.0.89.0, DataGate Component Suite 17.0.36.0 and 16.0.89.0, DataGate Monitor 17.0.26.0 and 16.0.65.0, DataGate WebPak 17.0.37.0 and 16.0.90.0, Monarch for .NET 11.4.50.0 and 10.0.62.0, Encore RPG 4.1.36.0, Visual RPG .NET FW 17.0.37.0 and 16.0.90.0, Visual RPG .NET FW Windows Deployment 17.0.36.0 and 16.0.89.0, WingsRPG 11.0.38.0 and 10.0.95.0, Mobile RPG 11.0.35.0 and 10.0.94.0, Monarch Framework for .NET FW 11.0.36.0 and 10.0.89.0, Browser Terminal 17.0.37.0 and 16.0.90.0, Visual RPG Classic 5.2.7.0 and 5.1.17.0, Visual RPG Deployment 5.2.7.0 and 5.1.17.0, and DataGate Studio 17.0.38.0 and 16.0.104.0.

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

ASNA Assist and ASNA Registrar Windows services contain unsafe deserialization vulnerabilities in their .NET remoting implementation. Attackers can exploit well-known .NET remoting deserialization flaws to execute arbitrary code with SYSTEM-level privileges, achieving privilege escalation. Multiple DataGate, Monarch, Visual RPG, and related product versions are affected.

MitigationDisable or remove the vulnerable ASNA Assist and ASNA Registrar services if .NET remoting is not required; otherwise, migrate away from deprecated .NET remoting to secure communication frameworks and implement allowlist-based deserialization filters.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

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 if ASNA Assist service is installed
    Open Services console (services.msc) and look for 'ASNA Assist' service, or run: Get-Service -Name '*ASNA*Assist*' in PowerShell
    Affected if The ASNA Assist service exists and is running on the system
  2. Identify if ASNA Registrar service is installed
    Open Services console (services.msc) and look for 'ASNA Registrar' service, or run: Get-Service -Name '*ASNA*Registrar*' in PowerShell
    Affected if The ASNA Registrar service exists and is running on the system
  3. Check installed ASNA product versions
    Check installed programs list or examine product version via: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*ASNA*'} | Select-Object DisplayName, DisplayVersion. Also check version via executable properties if located in Program Files
    Affected if Any installed ASNA product version falls within the vulnerable version ranges for DataGate, Monarch, Visual RPG, or related products
  4. Verify .NET remoting is enabled
    Examine ASNA service configuration files and application settings for .NET remoting endpoints. Check if the services expose remoting ports (default: 8200-8205 range for ASNA services). Use netstat -an | findstr '820' to check for listening ports
    Affected if The ASNA services have .NET remoting endpoints exposed and listening for incoming connections

The environment is affected if either the ASNA Assist or ASNA Registrar service is running and uses vulnerable .NET remoting with an affected ASNA product version installed.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable or remove the vulnerable ASNA Assist and ASNA Registrar services if .NET remoting is not required; otherwise, migrate away from deprecated .NET remoting to secure communication frameworks and implement allowlist-based deserialization filters.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43713 — 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-2025-43713 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