Skip to content
Fencer Intel
high 7.5

GHSA-m6m5-pp4g-fcc8 json

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

published 5y ago modified 8mo ago also GO-2022-0374

cvss
7.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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

Patch / fix

  • go github.com/foxcpp/maddy 0.5.1

Is GHSA-m6m5-pp4g-fcc8 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/foxcpp/maddy
<0.5.1
0.5.1

Classification

Weakness
  • CWE-772 Missing Release of Resource after Effective Lifetime

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.