# GHSA-6x4h-9622-fqr6: Improper validation in meraki


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Dec 2023

## What is GHSA-6x4h-9622-fqr6?

GHSA-6x4h-9622-fqr6 is a vulnerability in meraki, published on 13 Dec 2023. 

### Official description

aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Improper validation made it possible for an attacker to modify the HTTP request (e.g. to insert a new header) or create a new HTTP request if the attacker controls the HTTP version. The vulnerability only occurs if the attacker can control the HTTP version of the request. This issue has been patched in version 3.9.0.

meraki from version 1.40.1 requires aiohttp 3.9.0

## Which versions are affected by GHSA-6x4h-9622-fqr6?

2 open source packages ship an affected version, including meraki.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `meraki` | PyPI | All versions | 1.40.1 |
| `meraki` | PyPI | All versions | 1.40.1 |

## How do I fix GHSA-6x4h-9622-fqr6?

Upgrade meraki to 1.40.1 or later.

## Is GHSA-6x4h-9622-fqr6 being exploited?

There is no known exploitation of GHSA-6x4h-9622-fqr6 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-6x4h-9622-fqr6 and fix it if it is affected.

What it is: GHSA-6x4h-9622-fqr6 is a vulnerability in meraki, published on 13 Dec 2023. 
Exploitation: There is no known exploitation of GHSA-6x4h-9622-fqr6 in the wild and no public exploit code.

Affected packages and fixed versions:
- meraki (PyPI): affected all versions; fixed in 1.40.1
- meraki (PyPI): affected all versions; fixed in 1.40.1

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/GHSA-6x4h-9622-fqr6/ (Markdown: https://insights.sbomify.com/GHSA-6x4h-9622-fqr6/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-6x4h-9622-fqr6

---
From sbomify Insights: https://insights.sbomify.com/GHSA-6x4h-9622-fqr6/
Summaries are generated and may contain mistakes; the official description above is the record.