# CVE-2022-40319: Missing authorization in n/a

> Remote attackers can modify victim LISTSERV accounts by manipulating email addresses in URLs, requiring immediate patching by administrators.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 17 Jan 2023
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-mf9g-q8q5-vfm5

## What is CVE-2022-40319?

CVE-2022-40319 is a high-severity missing authorization vulnerability in n/a, published on 17 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The LISTSERV 17 web interface allows remote attackers to conduct Insecure Direct Object References (IDOR) attacks via a modified email address in a wa.exe URL. The impact is unauthorized modification of a victim's LISTSERV account.

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

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

It affects 1 product.


Products: Lsoft Listserv.

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

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

## Is CVE-2022-40319 being exploited?

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

Public exploit code:

- LISTSERV 17 - Insecure Direct Object Reference (IDOR) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0425](https://insights.sbomify.com/CVE-2000-0425/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-1044](https://insights.sbomify.com/CVE-2006-1044/): Memory corruption in n/a (high 7.5)
- [CVE-2005-1773](https://insights.sbomify.com/CVE-2005-1773/): Other in n/a (high 7.5)
- [CVE-2000-0632](https://insights.sbomify.com/CVE-2000-0632/): Memory corruption in n/a (high 7.5)
- [CVE-1999-0252](https://insights.sbomify.com/CVE-1999-0252/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40319 is a high-severity missing authorization vulnerability in n/a, published on 17 Jan 2023. 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-40319 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-40319/ (Markdown: https://insights.sbomify.com/CVE-2022-40319/index.md)
```

## Sources

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

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