Lucene search
+L

4 matches found

osv_ghsa
osv_ghsa
•added 2022/09/15 3:25 a.m.•41 views

GHSA-M77F-652Q-WWP4 axum-core has no default limit put on request bodies

::fromrequest would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a very large or infinite body your server might run out of memory and crash. This also applies to these extractors which used Bytes::fromrequest internally: -...

7.5CVSS7.4AI score0.01002EPSS
SaveExploits1References4
Github Security Blog
Github Security Blog
•added 2022/09/15 3:25 a.m.•42 views

axum-core has no default limit put on request bodies

::fromrequest would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a very large or infinite body your server might run out of memory and crash. This also applies to these extractors which used Bytes::fromrequest internally: -...

7.5CVSS7.3AI score0.01002EPSS
SaveExploits1References4Affected Software1
Cvelist
Cvelist
•added 2022/09/14 4:05 p.m.•63 views

CVE-2022-3212 DoS in axum-core due to missing request size limit

::fromrequest would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a very large or infinite body your server might run out of memory and crash. This also applies to these extractors which used Bytes::fromrequest internally:...

7.5CVSS7.7AI score0.01002EPSS
SaveExploits1References2
RustSec
RustSec
•added 2022/08/31 12:00 p.m.•35 views

No default limit put on request bodies

::fromrequest would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a very large or infinite body your server might run out of memory and crash. This also applies to these extractors which used Bytes::fromrequest internally: -...

7.5CVSS1.2AI score0.01002EPSS
SaveExploits1Affected Software1
Rows per page
Query Builder