This flaw allows a remote, low privileged attacker to force zgrep to write arbitrary files on the system. This flaw occurs due to insufficient validation when processing filenames with two or more newlines where selected content and the target file names are embedded in crafted multi-line file names. When zgrep is applied on the attacker's chosen file name (for example, a crafted file name), this can overwrite an attacker's content to an arbitrary attacker-selected file. See How to fix? for Debian:10 relevant fixed versions and status.Īn arbitrary file write vulnerability was found in GNU gzip's zgrep utility. Note: Versions mentioned in the description apply only to the upstream gzip package and not the gzip package as distributed by Debian:10. Upgrade Debian:10 zlib to version 1:1.2.11.dfsg-1+deb10u2 or higher. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference). NOTE: only applications that call inflateGetHeader are affected. Zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. See How to fix? for Debian:10 relevant fixed versions and status. Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Debian:10. Upgrade Debian:10 openssl to version 1.1.1n-0+deb10u3 or higher. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. This script is distributed by some operating systems in a manner where it is automatically executed. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. Upgrade Debian:10 openssl to version 1.1.1n-0+deb10u2 or higher. The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. Upgrade Debian:10 openssl to version 1.1.1d-0+deb10u7 or higher. The location of the buffer is application dependent but is typically heap allocated. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. ![]() The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. Typically an application will call this function twice. In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). ![]() ![]() Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian:10.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |