# CVE-2022-30763: Janet before 1.22.0 mishandles arrays.


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 16 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6vc7-fg29-7r6p

## What is CVE-2022-30763?

CVE-2022-30763 is a high-severity vulnerability in n/a, published on 16 May 2022. 

### Official description

Janet before 1.22.0 mishandles arrays.

Weakness: CWE-129 (Improper Validation of Array Index)

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

It affects 1 product.


Products: Janet-Lang Janet.

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

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

## Is CVE-2022-30763 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-2869](https://insights.sbomify.com/CVE-2026-2869/): janet-lang janet handleattr specials.c janetc_varset out-of-bounds (medium 4.8)
- [CVE-2026-2240](https://insights.sbomify.com/CVE-2026-2240/): janet-lang janet compile.c janetc_pop_funcdef out-of-bounds (medium 4.8)
- [CVE-2026-2241](https://insights.sbomify.com/CVE-2026-2241/): janet-lang janet os.c os_strftime out-of-bounds (medium 4.8)
- [CVE-2026-2242](https://insights.sbomify.com/CVE-2026-2242/): janet-lang janet specials.c janetc_if out-of-bounds (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30763 is a high-severity vulnerability in n/a, published on 16 May 2022. 
Exploitation: There is no known exploitation of CVE-2022-30763 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-30763/ (Markdown: https://insights.sbomify.com/CVE-2022-30763/index.md)
```

## Sources

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

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