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

> Attackers can obtain URIs to uploaded files by capturing POST responses, potentially leading to further exploitation.

- **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:** 16 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-23p4-5ppc-536p

## What is CVE-2022-24983?

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

### Official description

Forms generated by JQueryForm.com before 2022-02-05 allow remote attackers to obtain the URI to any uploaded file by capturing the POST response. When chained with CVE-2022-24984, this could lead to unauthenticated remote code execution on the underlying web server. This occurs because the Unique ID field is contained in the POST response upon submitting a form.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Jqueryform Jqueryform.

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

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

## Is CVE-2022-24983 being exploited?

There is no known exploitation of CVE-2022-24983 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-24984](https://insights.sbomify.com/CVE-2022-24984/): File upload in n/a (critical 9.8)
- [CVE-2022-24985](https://insights.sbomify.com/CVE-2022-24985/): Auth bypass in n/a (high 8.8)
- [CVE-2022-24982](https://insights.sbomify.com/CVE-2022-24982/): Information disclosure in n/a (medium 6.5)
- [CVE-2022-24981](https://insights.sbomify.com/CVE-2022-24981/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24983 is a high-severity vulnerability in n/a, published on 16 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24983 in the wild and no public exploit code.

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-24983/ (Markdown: https://insights.sbomify.com/CVE-2022-24983/index.md)
```

## Sources

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

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