# CVE-2023-33281: Other in n/a

> An attacker can replay RF signals to unlock Nissan Sylphy doors, though the vendor disputes the exploit's validity with genuine parts.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-mf42-cj9f-vmhp

## What is CVE-2023-33281?

CVE-2023-33281 is a medium-severity vulnerability in n/a, published on 22 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The remote keyfob system on Nissan Sylphy Classic 2021 sends the same RF signal for each door-open request, which allows for a replay attack. NOTE: the vendor's position is that this cannot be reproduced with genuine Nissan parts: for example, the combination of keyfob and door handle shown in the exploit demonstration does not match any technology that Nissan provides to customers.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 1 product.


Products: Nissan Sylphy Classic 2021 Firmware.

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

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

## Is CVE-2023-33281 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-33281 is a medium-severity vulnerability in n/a, published on 22 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-33281 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-33281/ (Markdown: https://insights.sbomify.com/CVE-2023-33281/index.md)
```

## Sources

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

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