# CVE-2022-26269: Other in n/a

> Attackers can tamper with displayed messages in Suzuki Connect by sending spoofed CAN messages, affecting vehicle user interfaces.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/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:** 29 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qw5m-84qm-7f97

## What is CVE-2022-26269?

CVE-2022-26269 is a medium-severity vulnerability in n/a, published on 29 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Suzuki Connect v1.0.15 allows attackers to tamper with displayed messages via spoofed CAN messages.

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

It affects 1 product.


Products: Globalsuzuki Suzuki Connect.

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

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

## Is CVE-2022-26269 being exploited?

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

Public exploit code:

- Suzuki connect app is used to get the car information like Fuel, Ignition status, Current location, Seat buckle status etc. In Ignis, Zeta variant car if the Fuel CAN messages and Seat buckle status is spoofed via OBD 2 port with the crafted value (e.g. zero percent fuel and Car seat is buckled ), then the same value is reflected on Suzuki connect app, which can mislead the user. (github_poc): https://github.com/nsbogam/CVE-2022-26269

## Fix prompt for AI coding agents

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

What it is: CVE-2022-26269 is a medium-severity vulnerability in n/a, published on 29 Mar 2022. 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-2022-26269 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-26269/ (Markdown: https://insights.sbomify.com/CVE-2022-26269/index.md)
```

## Sources

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

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