libp2p
The Rust Implementation of the libp2p networking stack.
View on Github
Activity
- Latest release
- 2d ago
- Total releases
- 105
- Cadence
- ~16 days
- Last 12 months
- 1
Reach
- Downloads
- 18.6M
- Stars
- 5.6k
Details
- License
- MIT
- First release
- Aug 08, 2018
| Version | Released | |
|---|---|---|
0.57.0
minor
|
0.57.0
minor
Dependencies (45)
+ 37 more
Changelog
Compare changes
|
|
0.56.0
unknown
|
0.56.0
unknown
Dependencies (45)
+ 37 more
Changelog
Compare changes
|
|
0.55.0
unknown
|
0.55.0
unknown
Dependencies (45)
+ 37 more
Changelog
Compare changes
|
|
0.54.1
unknown
|
0.54.1
unknown
Dependencies (48)
+ 40 more
Changelog
Compare changes
|
|
0.54.0
unknown
|
0.54.0
unknown
Dependencies (48)
+ 40 more
Changelog
Compare changes
|
|
0.53.2
unknown
|
0.53.2
unknown
Dependencies (49)
+ 41 more
Changelog
Compare changes
|
|
0.51.4
unknown
|
0.51.4
unknown
Dependencies (45)
+ 37 more
Changelog
Compare changes
|
|
0.53.1
unknown
|
0.53.1
unknown
Dependencies (49)
+ 41 more
Changelog
Compare changes
|
|
0.53.0
unknown
|
0.53.0
unknown
Dependencies (49)
+ 41 more
Changelog
Compare changes
|
|
0.52.4
unknown
|
0.52.4
unknown
Dependencies (52)
+ 44 more
Changelog
Compare changes
|
|
0.52.3
unknown
|
0.52.3
unknown
Dependencies (46)
+ 38 more
Changelog
Compare changes
|
|
0.52.2
unknown
|
0.52.2
unknown
Dependencies (45)
+ 37 more
Changelog
Compare changes
|
|
0.52.1
unknown
|
0.52.1
unknown
Dependencies (44)
+ 36 more
Changelog
Compare changes
|
|
0.52.0
unknown
|
0.52.0
unknown
Dependencies (43)
+ 35 more
Changelog
Compare changes
|
|
0.51.3
unknown
|
0.51.3
unknown
Dependencies (45)
+ 37 more
Changelog
Compare changes
|
|
0.51.2
unknown
|
0.51.2
unknown
Dependencies (45)
+ 37 more
Changelog
Compare changes
|
|
0.51.1
unknown
|
0.51.1
unknown
Dependencies (42)
+ 34 more
Changelog
Compare changes
|
|
0.50.1
unknown
|
0.50.1
unknown
Dependencies (42)
+ 34 more
Changelog
Compare changes
|
|
0.51.0
unknown
|
0.51.0
unknown
Dependencies (43)
+ 35 more
Changelog
Compare changes
|
|
0.50.0
unknown
|
0.50.0
unknown
Dependencies (42)
+ 34 more
Changelog
Compare changes
|
|
0.49.0
unknown
|
0.49.0
unknown
Dependencies (41)
+ 33 more
Changelog
Compare changes
|
|
0.48.0
unknown
|
0.48.0
unknown
Dependencies (42)
+ 34 more
Changelog
Compare changes
|
|
0.47.0
unknown
|
0.47.0
unknown
Dependencies (42)
+ 34 more
Changelog
Compare changes
|
|
0.46.1
unknown
|
0.46.1
unknown
Dependencies (42)
+ 34 more
Changelog
Compare changes
|
|
0.46.0
unknown
|
0.46.0
unknown
Dependencies (42)
+ 34 more
Changelog
Compare changes
|
|
0.45.1
unknown
|
0.45.1
unknown
Dependencies (42)
+ 34 more
Changelog
Compare changes
|
|
0.45.0
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.45.0
unknown
Dependencies (42)
+ 34 more
Changelog
Compare changes
|
|
0.44.0
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.44.0
unknown
Dependencies (43)
+ 35 more
Changelog
Compare changes
|
|
0.43.0
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.43.0
unknown
Dependencies (43)
+ 35 more
Changelog
Compare changes
|
|
0.41.2
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.41.2
unknown
Dependencies (41)
+ 33 more
Changelog
Compare changes
|
|
0.42.2
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.42.2
unknown
Dependencies (42)
+ 34 more
Changelog
Compare changes
|
|
0.42.1
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.42.1
unknown
Dependencies (42)
+ 34 more
Changelog
Compare changes
|
|
0.42.0
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.42.0
unknown
Dependencies (42)
+ 34 more
Changelog
Compare changes
|
|
0.41.1
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.41.1
unknown
Dependencies (41)
+ 33 more
Changelog
Compare changes
|
|
0.41.0
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.41.0
unknown
Dependencies (41)
+ 33 more
Changelog
Compare changes
|
|
0.40.0
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.40.0
unknown
Dependencies (38)
+ 30 more
Changelog
Compare changes
|
|
0.40.0-rc.3
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.40.0-rc.3
unknown
Dependencies (38)
+ 30 more
Changelog
Compare changes
|
|
0.40.0-rc.2
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.40.0-rc.2
unknown
Dependencies (38)
+ 30 more
Changelog
Compare changes
|
|
0.40.0-rc.1
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.40.0-rc.1
unknown
Dependencies (38)
+ 30 more
Changelog
Compare changes
|
|
0.39.1
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.39.1
unknown
Dependencies (34)
+ 26 more
Changelog
Compare changes
|
|
0.39.0
unknown
yanked
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.39.0
unknown
yanked
Dependencies (34)
+ 26 more
Changelog
Compare changes
|
|
0.38.0
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.38.0
unknown
Dependencies (34)
+ 26 more
Changelog
Compare changes
|
|
0.37.1
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.37.1
unknown
Dependencies (34)
+ 26 more
Changelog
Compare changes
|
|
0.37.0
unknown
yanked
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.37.0
unknown
yanked
Dependencies (34)
+ 26 more
Changelog
Compare changes
|
|
0.36.0
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.36.0
unknown
Dependencies (34)
+ 26 more
Changelog
Compare changes
|
|
0.35.1
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.35.1
unknown
Dependencies (33)
+ 25 more
Changelog
Compare changes
|
|
0.35.0
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.35.0
unknown
Dependencies (33)
+ 25 more
Changelog
Compare changes
|
|
0.34.0
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.34.0
unknown
Dependencies (33)
+ 25 more
Changelog
Compare changes
|
|
0.33.0
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.33.0
unknown
Dependencies (33)
+ 25 more
Changelog
Compare changes
|
|
0.32.2
unknown
1 CVE
CVE-2022-23486
GHSA-jvgw-gccv-q5p8
RUSTSEC-2022-0084
Dec 07, 2022
libp2p DoS vulnerability from lack of resource management
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
ImpactAn attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. DetailsIn the original version of the attack, the malicious node would continuously open new streams on a single connection using a stream multiplexer that doesn’t provide sufficient back pressure (mplex or yamux). While allocations per stream might be considered small, they multiply with the number of streams and connections. It is easy to defend against this one attack, e.g. by setting a strict per connection stream limit and connection limit. But there are other variations of this attack, e.g. causing memory allocations by sending partial payloads on various protocol levels, forcing the victim to buffer the partial payload for a period of time or by tricking the victim into pre-allocating buffers for messages which are never sent by the attacker. PatchesUsers are advised to upgrade to ReferencesPlease see our DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/. Please see the related disclosure for go-libp2p: https://github.com/libp2p/go-libp2p/security/advisories/GHSA-j7qp-mfxf-8xjw and js-libp2p: https://github.com/libp2p/js-libp2p/security/advisories/GHSA-f44q-634c-jvwv For more informationIf you have any questions or comments about this advisory, please email us at security@libp2p.io. Fixed in
0.45.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.32.2
unknown
Dependencies (33)
+ 25 more
Changelog
Compare changes
|