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

> Attackers can modify products owned by other sellers due to insecure direct object reference in the Online Market Place Site application.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-59vx-pp3g-92q8

## What is CVE-2022-29627?

CVE-2022-29627 is a medium-severity missing authorization vulnerability in n/a, published on 27 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An insecure direct object reference (IDOR) in Online Market Place Site v1.0 allows attackers to modify products that are owned by other sellers.

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

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

It affects 1 product.


Products: Online Market Place Site Project Online Market Place Site.

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

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

## Is CVE-2022-29627 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-30004](https://insights.sbomify.com/CVE-2022-30004/): SQL injection in n/a (critical 9.8)
- [CVE-2022-30003](https://insights.sbomify.com/CVE-2022-30003/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2022-29628](https://insights.sbomify.com/CVE-2022-29628/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29627 is a medium-severity missing authorization vulnerability in n/a, published on 27 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29627 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-29627/ (Markdown: https://insights.sbomify.com/CVE-2022-29627/index.md)
```

## Sources

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

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