dbcve.org
DevexpressApplication

CVE-2023-35817

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-28
Fix available
A fix is available. Upgrade to 21.2.12 or later.
See remediation →
100/100
Remediation priority · Urgent
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
DevExpress before 23.1.3 allows AsyncDownloader SSRF.

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

DevExpress UI component library before version 23.1.3 contains a Server-Side Request Forgery (SSRF) vulnerability in its AsyncDownloader component. An attacker can exploit this to make the server perform arbitrary HTTP requests to internal or external resources, potentially accessing sensitive internal services.

MitigationUpgrade DevExpress to version 23.1.3 or later to remediate the SSRF vulnerability in AsyncDownloader.

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
DevexpressApplication
Affected:< 21.2.12= 22.1.8= 22.2.4= 22.2.5

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 DevExpress installation and version
    Locate the DevExpress DLL files (typically DevExpress.Data*.dll or DevExpress.Web*.dll) in your application's bin directory or NuGet package references. Check the file properties or the packages.config/PackageReference to determine the installed version number.
    Affected if The installed version is < 21.2.12, or equals 22.1.8, 22.2.4, or 22.2.5.
  2. Confirm AsyncDownloader component usage
    Search your project source code and configuration files for references to 'AsyncDownloader', 'ASPxCloudControl', or related async download handlers. Inspect your web.config or app.config for custom handlers that may invoke this component.
    Affected if The AsyncDownloader component or related async download handler is actively used in your application.
  3. Verify exposed HTTP endpoints
    Review your application's URL routing and handler mappings (in web.config under system.webServer/handlers or system.web/httpHandlers) for any endpoints that expose the AsyncDownloader functionality to user requests.
    Affected if An HTTP endpoint that processes user-supplied URLs through AsyncDownloader is publicly accessible or reachable by untrusted users.
  4. Check for internal network requests
    Enable and review HTTP traffic logs or application tracing to observe whether the server is making outbound HTTP requests to arbitrary URLs provided via user input.
    Affected if The application allows user-influenced URLs to be passed to the AsyncDownloader without strict validation, enabling arbitrary HTTP requests.

You are affected if your environment runs a vulnerable DevExpress version AND the AsyncDownloader component is exposed and processes user-supplied URLs.

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 21.2.12 or later
Fixed in 21.2.12
Interim mitigation

Upgrade DevExpress to version 23.1.3 or later to remediate the SSRF vulnerability in AsyncDownloader.

Recommended fix High confidence

23.1.3 or later

  1. Identify the current DevExpress version in your application
  2. Review DevExpress 23.1.3 release notes and breaking changes for your specific product line
  3. Plan upgrade path considering your current version (e.g., 21.2.x -> 21.2.12 -> 22.1.x -> 22.2.x -> 23.1.3)
  4. Test the upgrade in a non-production environment first
  5. Verify AsyncDownloader functionality works as expected after upgrade
  6. Deploy to production
Caveat Review 23.1.3 release notes for product-specific breaking changes; major version upgrades may require code adjustments

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

Fix this in Devexpress Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,520
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,432.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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