CVE-2022-1897 Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.

CVE-2022-1897 Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.

This issue is due to the fact that the data protection mechanism operates on the file system level, so it is not possible to repair it at the moment. It is recommended to upgrade to the latest version of the editor. In order to decrease the risk of losing data due to software bugs, it is always recommended to keep the installed software up to date.
As soon as you have upgraded to the latest version of GitHub, you can restore the data to the repository by doing the following: Open the Settings menu and select the Accessibility option. Select the Out-of-bounds Write option and choose the Repository option from the list. Select the relevant repository and press the red “X” icon in the upper right corner. GitHub will warn you that the content has not been saved due to a software bug and that the data may be lost.

GitHub - Information leakage

GitHub was hit with a security issue on the fall of 22nd of December, 2028. A new version of their software was released and it was determined that there is a bug which leads to information leakage, but does not allow for data restoration.
The issue seems to be related to how the application handles invalid characters in text fields and accounts for cases with multiple lines. The problem can be found in the GitHub editor, which caused information to leak from around 500 repositories.

References

Subscribe to CVE.news
Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe