# GHSA-jrj9-5qp6-2v8q: Machine-In-The-Middle in airtable

> An attacker in a privileged network position can decrypt intercepted traffic because SSL certificate validation is disabled by default in the airtable library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2020

## What is GHSA-jrj9-5qp6-2v8q?

GHSA-jrj9-5qp6-2v8q is a vulnerability in airtable, published on 3 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Affected versions of `airtable` are vulnerable to Machine-In-The-Middle. The package has SSL certificate validation disabled by default unintentionally. This may allow attackers in a privileged network position to decrypt intercepted traffic.

## Recommendation

Upgrade to version 0.7.2 or later.

## Which versions are affected by GHSA-jrj9-5qp6-2v8q?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `airtable` | npm | From 0.1.19 | 0.7.2 |
| `airtable` | npm | From 0.1.19 | 0.7.2 |

## How do I fix GHSA-jrj9-5qp6-2v8q?

Upgrade airtable to 0.7.2 or later.

## Is GHSA-jrj9-5qp6-2v8q being exploited?

There is no known exploitation of GHSA-jrj9-5qp6-2v8q in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-jrj9-5qp6-2v8q and fix it if it is affected.

What it is: GHSA-jrj9-5qp6-2v8q is a vulnerability in airtable, published on 3 Sep 2020. 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 GHSA-jrj9-5qp6-2v8q in the wild and no public exploit code.

Affected packages and fixed versions:
- airtable (npm): affected from 0.1.19; fixed in 0.7.2
- airtable (npm): affected from 0.1.19; fixed in 0.7.2

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-jrj9-5qp6-2v8q/ (Markdown: https://insights.sbomify.com/GHSA-jrj9-5qp6-2v8q/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-jrj9-5qp6-2v8q

---
From sbomify Insights: https://insights.sbomify.com/GHSA-jrj9-5qp6-2v8q/
Summaries are generated and may contain mistakes; the official description above is the record.