Vulnerability in dojox (CVE-2019-10785)
Summary
Vulnerability in dojox (CVE-2019-10785). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
Impact
What kind of vulnerability is it? Who is impacted?
Potential XSS vulnerability for users of dojox/xmpp and dojox/dtl.
Patches
Has the problem been patched? What versions should users upgrade to?
Yes, patches are available for the 1.11 through 1.16 versions. Users should upgrade to one of these versions of Dojo:
- 1.16.1
- 1.15.2
- 1.14.5
- 1.13.6
- 1.12.7
- 1.11.9
Users of Dojo 1.10.x and earlier should review this change and determine if it impacts them, and backport the change as appropriate.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
The change applied in https://github.com/dojo/dojox/pull/315 could get added separately as a patch.
For more information
If you have any questions or comments about this advisory:
- Open an issue in dojo/dojox
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-2019-10785 has been found in dojox.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "dojox CVE-2019-10785" on the vendor's site.
CVE-2019-10785 (dojox)
Attack vector: remote (network-reachable) / unauthenticated
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.
A vulnerability (unclassified) exists in dojox.
Check the vendor advisory for the affected versions of dojox.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
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 'dojox' . 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 'dojox' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
dojoxを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2019-10785 dojo Fixed in: 1.15.2+dfsg1-1
References
- advisory snyk.io
- advisory nvd.nist.gov
- web lists.debian.org
- web github.com
- web github.com
- web github.com
- web snyk.io
- web snyk.io