Examples of using Memory corruption in English and their translations into Russian
{-}
-
Official
-
Colloquial
Memory corruption via session interruption.
Pinkie Pie discovered multiple memory corruption issues.
Memory corruption in regular expression comparison.
Wadih Matar discovered a memory corruption issue.
Memory corruption in an internal library may lead to denial of service.
These could lead to buffer overflows and memory corruption.
Christian Holler discovered a memory corruption in the v8 javascript library.
These could lead to buffer overflows and memory corruption.
Jeonghoon Shin discovered a memory corruption issue in the v8 javascript library.
This vulnerability allows attackers to execute code remotely and cause memory corruption.
Emilia Kaesper discovered a memory corruption in ASN.1 parsing.
It was discovered that a malformed EC private key might result in memory corruption.
Stefan Esser reported possible memory corruption in openssl_x509_parse.
Marc Schoenefeld discovered that profiling the JavaScript code could lead to memory corruption.
Christian Holler discovered a memory corruption issue in the v8 javascript library.
Memory corruption bugs could cause Icedove to crash or possibly execute arbitrary code.
Aki Helin andKhalil Zhani discovered a memory corruption issue in the ffmpeg library.
Description: A memory corruption issue was addressed through improved input validation.
It was discovered that missing input sanitising in base64 decoding might result in memory corruption.
Description: A memory corruption issue was addressed with improved memory handling.
But this simplicity is very deceptive and having saved a couple of seconds while writing the code,you will spend weeks to catch this elusive memory corruption error.
Bob Clary discovered memory corruption bugs, which may lead to the execution of arbitrary code.
The Web Audio implementation in Chromium before 27.0.1453.93 allows remote attackers to cause a denial of service(memory corruption) or possibly have unspecified other impact via unknown vectors.
Atte Kettunen discovered that a memory corruption bug in gfxImageSurface may lead to the execution of arbitrary code.
The reader uses QImage: :Format_Indexed8, but since the samples per pixel value this should be(non-existent) QImage::Format_Indexed16, causing memory corruption.
In some configurations, this would lead to memory corruption and crashes even without malicious traffic.
An attacker could execute arbitrary code via a PostScript file containing unlimited recursive procedure invocations,which trigger memory corruption in the stack of the interpreter.
Jesse Ruderman and Bob Clary discovered memory corruption bugs, which may lead to the execution of arbitrary code.
Ilja van Sprundel of IOActive discovered several security issues in multiple components of the X. org graphics stack and the related libraries: Various integer overflows, sign handling errors in integer conversions,buffer overflows, memory corruption and missing input sanitising may lead to privilege escalation or denial of service.
Mozilla developers discovered several memory corruption bugs, which may lead to the execution of arbitrary code.