# CVE-2023-2618: OpenCV wechat_qrcode Module decoded_bit_stream_parser.cpp decodeHanziSegment memory leak

> A memory leak in OpenCV's wechat_qrcode module allows remote attackers to cause denial of service via crafted QR codes.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 May 2023
- **Updated:** 2 Aug 2024
- **Also known as:** DEBIAN-CVE-2023-2618, GHSA-v2pm-rv6h-9g9p, JLSEC-2026-568, UBUNTU-CVE-2023-2618

## What is CVE-2023-2618?

CVE-2023-2618 is a medium-severity denial of service vulnerability in OpenCV wechat_qrcode Module, published on 10 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, has been found in OpenCV wechat_qrcode Module up to 4.7.0. Affected by this issue is the function DecodedBitStreamParser::decodeHanziSegment of the file qrcode/decoder/decoded_bit_stream_parser.cpp. The manipulation leads to memory leak. The attack may be launched remotely. The name of the patch is 2b62ff6181163eea029ed1cab11363b4996e9cd6. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-228548.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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

It affects 1 product.


Products: Opencv Opencv.

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

Apply the vendor's patch.

## Is CVE-2023-2618 being exploited?

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

## Other vulnerabilities in OpenCV wechat_qrcode Module

- [CVE-2019-5063](https://insights.sbomify.com/CVE-2019-5063/): Out-of-bounds Write in OpenCV (high 8.8)
- [CVE-2019-5064](https://insights.sbomify.com/CVE-2019-5064/): Out-of-bounds Write in OpenCV (high 8.8)
- [CVE-2019-14491](https://insights.sbomify.com/CVE-2019-14491/): Out-of-bounds Read in OpenCV (high 8.2)
- [CVE-2019-14492](https://insights.sbomify.com/CVE-2019-14492/): Out-of-bounds Read and Out-of-bounds Write in OpenCV (high 7.5)
- [CVE-2018-7712](https://insights.sbomify.com/CVE-2018-7712/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-2618 is a medium-severity denial of service vulnerability in OpenCV wechat_qrcode Module, published on 10 May 2023. 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-2023-2618 in the wild and no public exploit code.

Affected product: OpenCV wechat_qrcode Module. 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-2618/ (Markdown: https://insights.sbomify.com/CVE-2023-2618/index.md)
```

## Sources

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

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