Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

GHSA-m6m5-pp4g-fcc8 maddy

HIGH

GHSA-m6m5-pp4g-fcc8 is a high-severity (CVSS 7.5) vulnerability in github.com/foxcpp/maddy. A fix is available for github.com/foxcpp/maddy — see the affected versions and patch details below.

S3 storage write is not aborted on errors leading to unbounded memory usage

Also known asGO-2022-0374
Published
Oct 6, 2021
Updated
Aug 21, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Aug 21, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/foxcpp/maddy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Anyone using storage.blob.s3 introduced in 0.5.0 with storage.imapsql.

storage.imapsql local_mailboxes {
  ...
  msg_store s3 {
    ...
  }
}

Patches

The relevant commit is pushed to master and will be included in the 0.5.1 release.

No special handling of the issue has been done due to the small amount of affected users.

Workarounds

None.

References

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/foxcpp/maddyall versions0.5.1go get github.com/foxcpp/maddy@v0.5.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/foxcpp/maddy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/foxcpp/maddy to 0.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m6m5-pp4g-fcc8 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m6m5-pp4g-fcc8 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-m6m5-pp4g-fcc8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Anyone using storage.blob.s3 introduced in 0.5.0 with storage.imapsql. ``` storage.imapsql local_mailboxes { ... msg_store s3 { ... } } ``` ### Patches The relevant commit is pushed to master and will be included in the 0.5.1 release. No special handling of the issue has been done due to the small amount of affected users. ### Workarounds None. ### References * Original report: https://github.com/foxcpp/maddy/issues/395 * Fix: https://github.com/foxcpp/maddy/commit/07c8495ee4394fabbf5aac4df8aebeafb2fb29d8
O3 Security · Impact-Aware SCA

Is GHSA-m6m5-pp4g-fcc8 in your dependencies?

O3 Security finds GHSA-m6m5-pp4g-fcc8 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-m6m5-pp4g-fcc8: maddy (High 7.5) | O3 Security