Unsafe Deserialization in AjaxNetProfessional (CVE-2021-43853)
Summary
Vulnerability in AjaxNetProfessional (CVE-2021-43853). Confidential information can be exposed externally. Mitigation: upgrade to 21.12.22.1 or later.
Original description
The description as published by the source.
Overview
Affected versions of this package are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary JavaScript objects.
Description
Cross-Site Scripting (XSS) attacks are a type of injection, in which malicious scripts are injected into otherwise benign and trusted websites. XSS attacks occur when an attacker uses a web application to send malicious code, generally in the form of a browser side script, to a different end user. Flaws that allow these attacks to succeed are quite widespread and occur anywhere a web application uses input from a user within the output it generates without validating or encoding it.
XSS effects vary in range from petty nuisance to significant security risk, depending on the sensitivity of the data handled by the vulnerable site and the nature of any security mitigation implemented by the site's owner network.
Releases
Releases before version 21.12.22.1 are affected. Please be careful to download any binary DLL from other web sites, especially we found NuGet packages not owned by us that contain vulnerable versions.
Workarounds
A workaround exists that replaces one of the core JavaScript files embedded in the library. Using a XML configuration allows to replace the default JavaScript code to be replaced with the version on GitHub.
~/ajaxpro-core-fixed.js
Copy the file core.js from the main project folder to your web server root folde…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-43853 has been found in AjaxNetProfessional.
Confidential information can be exposed externally.
What to do: upgrade AjaxNetProfessional to 21.12.22.1 or later.
If unsure, ask your IT team or search "AjaxNetProfessional CVE-2021-43853" on the vendor's site.
CVE-2021-43853 (AjaxNetProfessional) — CWE-502
Attack vector: remote (network-reachable)
Patched: 21.12.22.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in AjaxNetProfessional.
Check the vendor advisory for the affected versions of AjaxNetProfessional.
Severity: ?. Confidential information can be exposed externally.
Update to 21.12.22.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'AjaxNetProfessional' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'AjaxNetProfessional' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
AjaxNetProfessionalを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade AjaxNetProfessional to 21.12.22.1ステージング環境で 21.12.22.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com