# GHSA-63rq-p8fp-524q: Potential API key leak

> An attacker can obtain API keys if location or weather APIs are unavailable, exposing sensitive credentials to IRC channels.

- **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:** 13 Apr 2021

## What is GHSA-63rq-p8fp-524q?

GHSA-63rq-p8fp-524q is a vulnerability in sopel-modules-weather, published on 13 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

If a user is actively blackholing the location or weather APIs, or those APIs become otherwise unavailable, it is possible for the API keys to get leaked to the active IRC channel.

This is patched in v1.2.4

## Which versions are affected by GHSA-63rq-p8fp-524q?

2 open source packages ship an affected version, including sopel-modules-weather and sopel-modules.weather.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sopel-modules-weather` | PyPI | All versions | 1.2.4 |
| `sopel-modules.weather` | PyPI | All versions | 1.2.4 |

## How do I fix GHSA-63rq-p8fp-524q?

Upgrade sopel-modules-weather to 1.2.4 or later.

## Is GHSA-63rq-p8fp-524q being exploited?

There is no known exploitation of GHSA-63rq-p8fp-524q in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-63rq-p8fp-524q and fix it if it is affected.

What it is: GHSA-63rq-p8fp-524q is a vulnerability in sopel-modules-weather, published on 13 Apr 2021. 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-63rq-p8fp-524q in the wild and no public exploit code.

Affected packages and fixed versions:
- sopel-modules-weather (PyPI): affected all versions; fixed in 1.2.4
- sopel-modules.weather (PyPI): affected all versions; fixed in 1.2.4

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-63rq-p8fp-524q/ (Markdown: https://insights.sbomify.com/GHSA-63rq-p8fp-524q/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-63rq-p8fp-524q

---
From sbomify Insights: https://insights.sbomify.com/GHSA-63rq-p8fp-524q/
Summaries are generated and may contain mistakes; the official description above is the record.