# CVE-2023-52727: Memory corruption in n/a

> An index out-of-range condition in the ONOS SD-RAN Go library allows attackers to cause memory corruption, potentially leading to crashes or code execution.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2024
- **Updated:** 3 Dec 2024
- **Also known as:** GHSA-wjjj-mh65-98qx

## What is CVE-2023-52727?

CVE-2023-52727 is a high-severity memory corruption vulnerability in n/a, published on 29 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Open Networking Foundation SD-RAN ONOS onos-lib-go 0.10.25 allows an index out-of-range condition in parseAlignBits.

Weakness: CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Linuxfoundation Onos-Lib-Go.

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

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

## Is CVE-2023-52727 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-52728](https://insights.sbomify.com/CVE-2023-52728/): Other in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-52727 is a high-severity memory corruption vulnerability in n/a, published on 29 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52727 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-2023-52727/ (Markdown: https://insights.sbomify.com/CVE-2023-52727/index.md)
```

## Sources

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

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