# CVE-2022-41479: Information disclosure in n/a

> An IDOR vulnerability in DevExpress ASP.NET allows attackers to access client-side application source code via the resource handler.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2022
- **Updated:** 15 May 2025
- **Also known as:** GHSA-6prj-5r8w-3x38

## What is CVE-2022-41479?

CVE-2022-41479 is a high-severity vulnerability in n/a, published on 18 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The DevExpress Resource Handler (ASPxHttpHandlerModule) in DevExpress ASP.NET Web Forms Build v19.2.3 does not verify the referenced objects in the /DXR.axd?r= HTTP GET parameter. This leads to an Insecure Direct Object References (IDOR) vulnerability which allows attackers to access the application source code. NOTE: the vendor disputes this because the retrieved source code is only the DevExpress client-side application code that is, of course, intentionally readable by web browsers (a site's custom code and data is never accessible via an IDOR approach).

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2022-41479?

It affects 1 product.


Products: Devexpress Asp.net Web Forms Controls.

## How do I fix CVE-2022-41479?

No fix has been published for CVE-2022-41479 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41479 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41479 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41479 and fix it if it is affected.

What it is: CVE-2022-41479 is a high-severity vulnerability in n/a, published on 18 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41479 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41479/ (Markdown: https://insights.sbomify.com/CVE-2022-41479/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41479
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41479
- OSV: https://osv.dev/vulnerability/CVE-2022-41479

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41479/
Summaries are generated and may contain mistakes; the official description above is the record.