Hotlinking Vulnerability in PHProxy 0.5b2

Posted by Celso Bento on Jan 09

A flaw exists in PHProxy 0.5b2 hotlinking feature which allow anyone using
some coding to link to proxified pages.

By default hotlinking is active to prevent users from retrieving pages
directly from the proxy requiring them to use the form. This can be easily
bypassed.

This is the same type of vulnerability found on Glype 1.4.4. Other
webproxies may be vulnerable too…

enigma2-plugin-extensions-webadmin Remote Code Execution (IoT)

Posted by Fabian Fingerle on Jan 09

enigma2-plugin-extensions-webadmin Remote Code Execution

Severity: CRITICAL/TRIVIAL

Discovered by:
Fabian Fingerle (@otih__)
https://fabian-fingerle.de

enigma2-plugin-extensions-webadmin:
The enigma2-plugin-extensions-webadmin Plugin is a web frontend for the
OPKG or APT package manager. With the webadmin it’s possible to install
or remove packages, and many other functions over the webinterface of
the Dreambox. Therefore Enigma2 is the…

pev 0.80 released

Posted by Fernando Mercês on Jan 09

Hi there!

This is to let you guys know we just released a new version of pev, our
open source, multi-platform toolkit to analyze PE files. We do have a hard
mission: analyze PE files without relaying on Windows API but we’ve been
achieving this with our own PE library that we called libpe, written
entirely in C, just like all other pev tools.

We’d love to hear your feedback, if you have some.

Website: http://pev.sf.net
Code:…

BSides Las Vegas 2017 CFP is open.

Posted by Daemon Tamer on Jan 09

The CFP for BSides Las Vegas 2017 is currently open at
https://bsideslv.org/openconf/openconf.php.

We’re accepting proposals for the following tracks:

Breaking Ground – Ground Breaking Information Security research and
conversations on the “Next Big Thing”. Interactively discussing your
research with our participants and getting feedback, input and opinion. No
preaching from the podium at a passive audience.

Common Ground – Other…

CVE-2016-6580

A HTTP/2 implementation built using any version of the Python priority library prior to version 1.2.0 could be targeted by a malicious peer by having that peer assign priority information for every possible HTTP/2 stream ID. The priority tree would happily continue to store the priority information for each stream, and would therefore allocate unbounded amounts of memory. Attempting to actually use a tree like this would also cause extremely high CPU usage to maintain the tree. (CVSS:5.0) (Last Update:2017-01-27)