# CVE-2023-29492: Novi Survey Insecure Deserialization

> Remote attackers can execute arbitrary code on the server via the Novi Survey application, requiring an upgrade to mitigate.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 13 Apr 2023 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-6p4p-p9hh-3hq7

## What is CVE-2023-29492?

CVE-2023-29492 is a critical code injection vulnerability in n/a, published on 11 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Novi Survey before 8.9.43676 allows remote attackers to execute arbitrary code on the server in the context of the service account. This does not provide access to stored survey or response data.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2023-29492?

It affects 1 product.


Products: 3rdmill Novi Survey.

## How do I fix CVE-2023-29492?

No fix has been published for CVE-2023-29492 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 4 May 2023.

## Is CVE-2023-29492 being exploited?

Yes. Attackers have exploited CVE-2023-29492 in the wild since at least 13 Apr 2023.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29492 and fix it if it is affected.

What it is: CVE-2023-29492 is a critical code injection vulnerability in n/a, published on 11 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-29492 in the wild since at least 13 Apr 2023.

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

## Sources

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

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