Skip to content
Fencer Intel
low —

GHSA-v7hc-87jc-qrrr json

eventing-github vulnerable to denial of service caused by improper enforcement of the timeout on individual read operations

published 2y ago modified 8mo ago also GO-2023-2388

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

Summary

### Impact

The eventing-github cluster-local server doesn't set `ReadHeaderTimeout`‬‭ which could lead do a DDoS‬ ‭attack, where a large group of users send requests to the server causing the server to hang‬ ‭for long enough to deny it from being available to other users, also know as a Slowloris‬ ‭attack.

### Patches

Fix in `v1.12.1` and `v1.11.3`

### Credits

The vulnerability was reported by Ada Logics during an ongoing security audit of Knative involving Ada Logics, the Knative maintainers, OSTIF and CNCF.

Patch / fix

  • go knative.dev/eventing-github 0.39.1

Is GHSA-v7hc-87jc-qrrr 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

Affected packages

ecosystem package affected fixed in
go knative.dev/eventing-github
<0.39.1
0.39.1

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

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.