CVE-2022-28506 There is a heap-buffer-overflow in GIFLIB 5.2.1 function DumpScreen2RGB() in gif2rgb.c:298:45.

CVE-2022-28506 There is a heap-buffer-overflow in GIFLIB 5.2.1 function DumpScreen2RGB() in gif2rgb.c:298:45.

This could allow an attacker to take control of the application or cause a denial of service. It has been reported to fixed in version 5.2.2. The heap-buffer-overflow occurs in function DumpScreen2RGB() in gif2rgb.c:298:45. This could allow an attacker to take control of the application or cause a denial of service. It has been reported to fixed in version 5.2.2. The heap-buffer-overflow occurs in function DumpScreen2RGB() in gif2rgb.c:298:45. Line 298 of gif2rgb.c: 298 /* We don’t want to print the whole screen, only the part that needs it. */ - screen_size = screen_size / 2; /* We don’t want to print the whole screen, only the part that needs it. */ - screen_size = screen_size / 2;

An attacker can cause a heap-buffer-overflow by sending a large amount of data to the application and can cause a denial of service by sending a large amount of data to the application that could cause the application to crash. An attacker can cause a heap-buffer-overflow by sending a large amount of data to the application and can cause a denial of service by sending a large amount of data to the application that could cause the application to crash. Line 298 of gif2rgb.c:

Vulnerability summary

This could allow an attacker to take control of the application or cause a denial of service. It has been reported to fixed in version 5.2.2. The heap-buffer-overflow occurs in function DumpScreen2RGB() in gif2rgb.c:298:45.

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