Prysm has 1 public audit report from Quantstamp; dated 13 Oct 2020; no critical findings reported.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Statuses are the security firms’ own
10 findings are still open or acknowledged in the firms’ reports: 1 high, 3 medium, 6 low (3 open, 7 acknowledged).
Insecure gRPC connection by default
Prysm · Quantstamp · 13 Oct 2020 · Report ↗
DDoS attack vector through creating a mapping between public keys and validators’ IPs
Prysm · Quantstamp · 13 Oct 2020 · Report ↗
Lack of unit tests
Prysm · Quantstamp · 13 Oct 2020 · Report ↗
Second pre-image attack on Merkle Trees
Prysm · Quantstamp · 13 Oct 2020 · Report ↗
Minimal system requirements
Prysm · Quantstamp · 13 Oct 2020 · Report ↗
Number of bad responses is not incremented in the `Goodbye` topic
Prysm · Quantstamp · 13 Oct 2020 · Report ↗
Running out of disk space
Prysm · Quantstamp · 13 Oct 2020 · Report ↗
Boot nodes availability and centralization risks
Prysm · Quantstamp · 13 Oct 2020 · Report ↗
Disk space exhaustion attack
Prysm · Quantstamp · 13 Oct 2020 · Report ↗
Peer descoring and disconnect on failed validation, while being optional in the spec, should be considered
Prysm · Quantstamp · 13 Oct 2020 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| Prysm | Security firm: Quantstamp | Date: | Scope: Files listed | None open | Findings: 4 high · 12 medium · 20 low 25 fixed · 7 acknowledged · 3 open | certificate.quantstamp.com ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed | Mitigated |
|---|---|---|---|---|
| Critical | 0 | 0 | 0 | 0 |
| High | 0 | 1 | 3 | 0 |
| Medium | 0 | 3 | 9 | 0 |
| Low | 3 | 3 | 13 | 1 |
Upon start, beacon-node does not check if minimal system requirements are met. Validators may not be aware of system requirements; if many validators face the same issue, the whole network may not perform as expected.
Open the reportAccording to the specification _in case of an invalid input, a reader MUST:_ * _From responses: ignore the response, the response MUST be considered bad server behavior._ The number of bad responses is incremented for all topics with the exception of the `Goodbye` topic, whose handlers are in `beacon-chain/sync/rpc_goodbye.go`
Open the reportWhen the beacon node removes data in the database (e.g., when pruning garbage state), the corresponding space in disk is not freed, as BoltDB does NOT perform any clean-up.
Open the reportThe reports name a repository or files. Open a report to see its scope.
Trustblock holds 1 public audit report for Prysm, dated 13 Oct 2020. The latest is by Quantstamp (“Prysm”).
Quantstamp wrote the report Trustblock holds for Prysm.
10 findings are still open or acknowledged in the firms’ reports: 1 high, 3 medium, 6 low (3 open, 7 acknowledged). No critical finding is reported. Statuses are the security firms’ own.
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="prysm"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us