# OSV-2020-1573: Use-of-uninitialized-value in void ArduinoJsonNUMBER_71::Utf8::encodeCodepoint<ArduinoJsonNUMBER_71::StringCop

> An attacker can cause a denial of service in applications using ArduinoJson by triggering a use-of-uninitialized-value error during JSON deserialization.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2020

## What is OSV-2020-1573?

OSV-2020-1573 is a vulnerability in arduinojson, published on 4 Aug 2020. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=24633

```
Crash type: Use-of-uninitialized-value
Crash state:
void ArduinoJsonNUMBER_71::Utf8::encodeCodepoint<ArduinoJsonNUMBER_71::StringCop
ArduinoJsonNUMBER_71::JsonDeserializer<ArduinoJsonNUMBER_71::BoundedReader<unsig
ArduinoJsonNUMBER_71::JsonDeserializer<ArduinoJsonNUMBER_71::BoundedReader<unsig
```

## Which versions are affected by OSV-2020-1573?

1 open source package ship an affected version, including arduinojson.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `arduinojson` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2020-1573?

No fix has been published for OSV-2020-1573 yet. Limit exposure of the affected software until one is available.

## Is OSV-2020-1573 being exploited?

There is no known exploitation of OSV-2020-1573 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2020-1573 and fix it if it is affected.

What it is: OSV-2020-1573 is a vulnerability in arduinojson, published on 4 Aug 2020. 
Exploitation: There is no known exploitation of OSV-2020-1573 in the wild and no public exploit code.

Affected packages and fixed versions:
- arduinojson (OSS-Fuzz): affected all versions; 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/OSV-2020-1573/ (Markdown: https://insights.sbomify.com/OSV-2020-1573/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2020-1573

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