First up, git has been audited . This was an effort sponsored by the Open Source Technology Improvement Fund (OSTIF), a non-profit working to improve the security of Open Source projects. The audit itself was done by researchers from X41 and GitLab, and two critical vulnerabilities were found , both caused by the same bad coding habit — using an int to hold buffer lengths. On modern systems, a size_t is always unsigned, and the same bit length as the architecture bit-width. This is the proper data type for string and buffer lengths, as it is guaranteed not to overflow when handling lengths up to the maximum addressable memory on the system. On the other hand, an int is usually four bytes long and signed, with a maximum value of 2^31-1, or 2147483647 — about 2 GB. A big buffer, but not an unheard amount of data. Throw something that large at git, and it will break in unexpected ways. Our first example is CVE-2022-23521, an out of bounds write caused by an int overflowing to negat...
I am impressed by the information that you have on this blog. Thank you for sharing. The smoother the screen will look to the human eye, the higher the number. A 120Hz display, which updates itself 120 times per second, will therefore appear noticeably smoother and more natural than a typical 60Hz panel, which refreshes itself just 60 times each second. Read more about Refresh rate.
ReplyDelete