# CVE-2010-1666: Improper Restriction of Operations within the Bounds of a Memory Buffer in python-cjson

> A buffer overflow in python-cjson allows attackers to cause a crash or potentially execute code via crafted Unicode input when UCS-4 encoding is enabled.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jul 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-2068-1, GHSA-cqmh-mpx2-g633, PYSEC-2010-30, openSUSE-SU-2024:11259-1

## What is CVE-2010-1666?

CVE-2010-1666 is a medium-severity memory corruption vulnerability in n/a, published on 2 Jul 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in Dan Pascu python-cjson 1.0.5, when UCS-4 encoding is enabled, allows context-dependent attackers to cause a denial of service (application crash) or possibly have unspecified other impact via vectors involving crafted Unicode input to the cjson.encode function.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2010-1666?

3 open source packages ship an affected version, including python-cjson. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-cjson` | PyPI | All versions | 1.0.5.1 |
| `python-cjson` | PyPI | All versions | 1.0.5.1 |
| `python-cjson` | PyPI | All versions | 1.1.0 |

Products: Dan Pascu Python-Cjson.

## How do I fix CVE-2010-1666?

Upgrade python-cjson to a fixed version for your release line: 1.0.5.1 or 1.1.0.

## Is CVE-2010-1666 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4924](https://insights.sbomify.com/CVE-2009-4924/): Cross-site Scripting in python-cjson (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1666 and fix it if it is affected.

What it is: CVE-2010-1666 is a medium-severity memory corruption vulnerability in n/a, published on 2 Jul 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-1666 in the wild and no public exploit code.

Affected packages and fixed versions:
- python-cjson (PyPI): affected all versions; fixed in 1.0.5.1
- python-cjson (PyPI): affected all versions; fixed in 1.0.5.1
- python-cjson (PyPI): affected all versions; fixed in 1.1.0

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

## Sources

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

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