# GHSA-7543-mr7h-6v86: Improper Authorization in googleapis

> Improper authorization in googleapis library allows requests to use incorrect credentials, potentially bypassing security controls and exposing data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Sep 2020

## What is GHSA-7543-mr7h-6v86?

GHSA-7543-mr7h-6v86 is a missing authorization vulnerability in googleapis, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `googleapis` prior to 39.1.0 are vulnerable to Improper Authorization. Setting credentials to one client may apply to all clients which may cause requests to be sent with the incorrect credentials.

## Recommendation

Upgrade to version 39.1.0.

## Which versions are affected by GHSA-7543-mr7h-6v86?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `googleapis` | npm | All versions | 39.1.0 |
| `googleapis` | npm | All versions | 39.1.0 |

## How do I fix GHSA-7543-mr7h-6v86?

Upgrade googleapis to 39.1.0 or later.

## Is GHSA-7543-mr7h-6v86 being exploited?

There is no known exploitation of GHSA-7543-mr7h-6v86 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-7543-mr7h-6v86 and fix it if it is affected.

What it is: GHSA-7543-mr7h-6v86 is a missing authorization vulnerability in googleapis, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-7543-mr7h-6v86 in the wild and no public exploit code.

Affected packages and fixed versions:
- googleapis (npm): affected all versions; fixed in 39.1.0
- googleapis (npm): affected all versions; fixed in 39.1.0

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-7543-mr7h-6v86/ (Markdown: https://insights.sbomify.com/GHSA-7543-mr7h-6v86/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-7543-mr7h-6v86

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