0day.today - Biggest Exploit Database in the World.
- We use one main domain: http://0day.today
- Most of the materials is completely FREE
- If you want to purchase the exploit / get V.I.P. access or pay for any other service,
you need to buy or earn
GOLD
Administration of this site uses the official contacts. Beware of impostors!
We DO NOT use Telegram or any messengers / social networks!Please, beware of scammers!
- Read the [ agreement ]
- Read the [ Submit ] rules
- Visit the [ faq ] page
- [ Register ] profile
- Get [ GOLD ]
- If you want to [ sell ]
- If you want to [ buy ]
- If you lost [ Account ]
- Any questions [ admin@0day.today ]
- Authorisation page
- Registration page
- Restore account page
- FAQ page
- Contacts page
- Publishing rules
- Agreement page
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
Contact us
You can contact us by:
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
Jaws 1.1.1 Code Execution Vulnerability
[1. Introduction Affected Product: Jaws 1.1.1 Fixed in: not fixed Fixed Version Link: n/a Vendor Website: http://jaws-project.com/ Vulnerability Type: Code Execution Remote Exploitable: Yes Reported to vendor: 09/05/2016 Disclosed to public: 11/10/2016 Release mode: Full Disclosure CVE: n/a Credits Tim Coen of Curesec GmbH 2. Overview Jaws is a content management system written in PHP. In version 1.1.1, it is vulnerable to code execution as it allows the upload of files with a dangerous type. An account with extended privileges is required. 3. Details CVSS: High 9.0 AV:N/AC:L/Au:S/C:C/I:C/A:C The file manager forbids the uploading of most PHP and htaccess files by checking the extension of uploaded files and renaming files when required. However, the check can be bypassed by an attacker as the file extension .pht - which is treated as PHP file by default Apache installations - is not filtered. An account with access to the file manager is required. 4. Solution This issue was not fixed by the vendor. 5. Report Timeline 09/05/2016 Informed Vendor about Issue (no reply) 09/15/2016 Reminded Vendor of Disclosure Date (no reply) 11/10/2016 Disclosed to public Blog Reference: https://www.curesec.com/blog/article/blog/Jaws-111-Code-Execution-170.html # 0day.today [2024-12-25] #