# CVE-2022-4772: Widoco WidocoUtils.java unZipIt path traversal

> A path traversal vulnerability in Widoco's unZipIt function allows local attackers to read or modify arbitrary files.

- **Severity:** Medium 4.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Dec 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jj8r-jw42-mw4w

## What is CVE-2022-4772?

CVE-2022-4772 is a medium-severity path traversal vulnerability in Widoco, published on 27 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in Widoco and classified as critical. Affected by this issue is the function unZipIt of the file src/main/java/widoco/WidocoUtils.java. The manipulation leads to path traversal. It is possible to launch the attack on the local host. The name of the patch is f2279b76827f32190adfa9bd5229b7d5a147fa92. It is recommended to apply a patch to fix this issue. VDB-216914 is the identifier assigned to this vulnerability.

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

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

2 open source packages ship an affected version, including com.github.dgarijo:Widoco. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.github.dgarijo:Widoco` | Maven | All versions to 1.4.17 | None |
| `com.github.dgarijo:Widoco` | Maven | All versions to 1.4.17 | None |

Products: Widoco Project Widoco.

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

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

## Is CVE-2022-4772 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4772 is a medium-severity path traversal vulnerability in Widoco, published on 27 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4772 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.github.dgarijo:Widoco (Maven): affected all versions up to 1.4.17; no fix listed
- com.github.dgarijo:Widoco (Maven): affected all versions up to 1.4.17; no fix listed

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

## Sources

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

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