![]() ![]() MFSA 2012-88 Miscellaneous memory safety hazards (rv:16.0.1) ![]() MFSA 2012-87 Use-after-free in the IME State Manager MFSA 2012-86 Heap memory corruption issues found using Address Read issues found using Address Sanitizer MFSA 2012-85 Use-after-free, buffer overflow, and out of bounds MFSA 2012-84 Spoofing and script injection through location.hash MFSA 2012-83 Chrome Object Wrapper (COW) does not disallow acces ![]() MFSA 2012-82 top object and location property accessible by MFSA 2012-81 GetProperty function can bypass security checks MFSA 2012-80 Crash with invalid cast when using instanceof MFSA 2012-79 DOS and crash with full screen and history navigation MFSA 2012-78 Reader Mode pages have chrome privileges MFSA 2012-77 Some DOMWindowUtils methods bypass security checks MFSA 2012-76 Continued access to initial origin after setting MFSA 2012-75 select element persistance allows for attacks MFSA 2012-74 Miscellaneous memory safety hazards (rv:16.0/ Critical CVE-2012-5112: SVG use-after-free and CVE-2012-5339 CVE-2012-5368 chromium - multiple vulnerabilities chromium. Man-in-the-middle could modify this script on the wire toĬause mischief. Version on the main page, a piece of JavaScript is fetchedįrom the website in non-SSL mode. To display information about the current phpMyAdmin With a crafted name, it is possible to trigger an XSS. When creating/modifying a trigger, event or procedure CVE-2012-4506 !topic/gitolite/K9SnQNhCQ-0/discussion phpMyAdmin - Multiple XSS due to unescaped HTML output in Trigger, Procedure and Event pages and Fetching the version information from a non-SSL site is vulnerable to a MITM attack phpMyAdmin 3.5 3.5.3 Otherwise the worst he can do is create arbitrary repos in /tmp. Userid on the same box), can compromise the entire "git" user. How badly can it affect you? A malicious user who *also* has theĪbility to create arbitrary files in, say, /tmp (e.g., he has his own Thanks to Stephane Chazelas for finding it and alerting me.Ĭan it affect you? This can only affect you if you are using wildĬard repos, *and* at least one of your patterns allows the string I'm sorry to say there is a potential path traversal vulnerability in ![]()
0 Comments
Leave a Reply. |