# CVE-2022-41763: Code injection in n/a

> Authenticated remote attackers can inject code into the PING function via the ipAddress variable, leading to remote code execution on the Nokia AMS server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 5 Sep 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3r46-8fph-p95v

## What is CVE-2022-41763?

CVE-2022-41763 is a high-severity code injection vulnerability in n/a, published on 5 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in NOKIA AMS 9.7.05. Remote Code Execution exists via the debugger of the ipAddress variable. A remote user, authenticated to the AMS server, could inject code in the PING function. The privileges of the command executed depend on the user that runs the service.

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

## Which versions are affected by CVE-2022-41763?

It affects 1 product.


Products: Nokia Access Management System.

## How do I fix CVE-2022-41763?

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

## Is CVE-2022-41763 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41763 and fix it if it is affected.

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

## Sources

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

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