Search...

Joomla DT Register Component - cat SQL Injection Vulnerability

2016-12-13T00:00:00

ID 1337DAY-ID-26520
Type zdt
Reporter Elar Lang
Modified 2016-12-13T00:00:00

Description

Exploit for php platform in category web applications

                                        
                                            Title: SQL injection in Joomla extension DT Register
Credit: Elar Lang / https://security.elarlang.eu
Vulnerability: SQL injection
Vulnerable version: before 3.1.12 (Joomla 3.x) / 2.8.18 (Joomla 2.5)
CVE: pending
Full Disclosure URL: https://security.elarlang.eu/sql-injection-in-joomla-extension-dt-register.html
Vendor: DTH Development
Vendor URL: http://www.dthdevelopment.com/
Product: DT Register "Calendar & Event Registration"
Product URL: https://extensions.joomla.org/extension/dt-register
Product URL: http://www.dthdevelopment.com/joomla-components/dt-register-event-registration-for-joomla.html
 
 
# Background
 
"DT Register is the Joomla Event Registration component that gives you
functionality beyond what any other event booking solution can offer"
(https://extensions.joomla.org/extension/dt-register)
 
 
# Vulnerability
 
SQL injection in Joomla extension "DT Register" by DTH Development
allows remote unauthenticated attacker to execute arbitrary SQL
commands via the cat parameter.
 
 
# Preconditions
 
No pre-conditions for authentication or authorization.
 
 
# Proof-of-Concept
 
http://[DOMAIN]/[PATH]/index.php?controller=calendar&format=raw&cat[0]=SQLi&task=events
 
PoC value (shows out all events / it's possible to see valid eventId values):
cat[0]=6) OR 1-- -
 
 
## Using UNION
 
For reading the data out using UNION it's important to have and to
know one valid eventId (detected in previous step).
 
In total there are 112 fields in select query, eventId position is no
13. For output is best to use position 112.
 
Step-by-Step - how to read the data out is available in blog:
https://security.elarlang.eu/sql-injection-in-joomla-extension-dt-register.html
 
 
# Vulnerability Disclosure Timeline
 
Full communication is available in blog:
https://security.elarlang.eu/sql-injection-in-joomla-extension-dt-register.html
 
2016-10-17 | me &gt; DTH | via web form - I would like to report some
security holes. What is the correct way for that?
2016-10-18 | me &gt; DTH | any response?
2016-10-25 | me &gt; DTH | mail to [email protected]
2016-10-25 | DTH &gt; me |
* "you are not in our client list"
* "Our site (dthdevelopment.com) is protected by an enterprise grade firewall"
2016-10-25 | me &gt; DTH | I'm whitehat, technical details
2016-10-25 | DTH &gt; me | description, what kind of serious problems I may face
2016-10-25 | me &gt; DTH | explanations
2016-11-02 | me &gt; DTH | hello?
2016-11-11 | me &gt; DTH, SiteLock | Last call.
2016-11-11 | SiteLock / DTH / me | some communication
2016-11-12 | DTH &gt; SiteLock (CC to me) | "It was configured to be open
in the setup"
2016-11-15 | DTH | Released DT Register version 3.1.12 (J3.x) / 2.8.18 (J2.5)
2016-12-05 | DTH &gt; me | "Sorry, forgot to respont on this. We closed
the problem on our demo site".
2016-12-12 | me | Full Disclosure on security.elarlang.eu
2016-12-13 | me | Full Disclosure on FullDisclosure mailinglist on seclists.org
 
 
## asking CVE from DWF (Distributed Weakness Filing Project) /
http://iwantacve.org
 
2016-10-20 | me &gt; DWF | CVE request
2016-10-31 | DWF &gt; me | "CVE - Acceptance of MITRE Terms of Use for
CVE Assignment"
2016-10-31 | me &gt; DWF | I accept
2016-11-19 | me &gt; DWF | Any feedback or decision? (still no response)
2016-12-11 | me &gt; DWF | Is there any hope to get feedback?  (still no response)
 
As I haven't got any feedback, you can take this post as CVE request.
 
 
# Fix
DT Register version 3.1.12 (J3.x) / 2.8.18 (J2.5).

#  0day.today [2018-04-12]  #

JSON Vulners Source

Initial Source

{"enchantments": {"score": {"value": 0.0, "vector": "NONE", "modified": "2018-04-12T07:53:46", "rev": 2}, "dependencies": {"references": [], "modified": "2018-04-12T07:53:46", "rev": 2}, "vulnersScore": 0.0}, "bulletinFamily": "exploit", "references": [], "href": "https://0day.today/exploit/description/26520", "id": "1337DAY-ID-26520", "title": "Joomla DT Register Component - cat SQL Injection Vulnerability", "type": "zdt", "cvss": {"score": 0.0, "vector": "NONE"}, "lastseen": "2018-04-12T07:53:46", "edition": 1, "sourceHref": "https://0day.today/exploit/26520", "reporter": "Elar Lang", "description": "Exploit for php platform in category web applications", "modified": "2016-12-13T00:00:00", "viewCount": 21, "published": "2016-12-13T00:00:00", "cvelist": [], "sourceData": "Title: SQL injection in Joomla extension DT Register\r\nCredit: Elar Lang / https://security.elarlang.eu\r\nVulnerability: SQL injection\r\nVulnerable version: before 3.1.12 (Joomla 3.x) / 2.8.18 (Joomla 2.5)\r\nCVE: pending\r\nFull Disclosure URL: https://security.elarlang.eu/sql-injection-in-joomla-extension-dt-register.html\r\nVendor: DTH Development\r\nVendor URL: http://www.dthdevelopment.com/\r\nProduct: DT Register \"Calendar & Event Registration\"\r\nProduct URL: https://extensions.joomla.org/extension/dt-register\r\nProduct URL: http://www.dthdevelopment.com/joomla-components/dt-register-event-registration-for-joomla.html\r\n \r\n \r\n# Background\r\n \r\n\"DT Register is the Joomla Event Registration component that gives you\r\nfunctionality beyond what any other event booking solution can offer\"\r\n(https://extensions.joomla.org/extension/dt-register)\r\n \r\n \r\n# Vulnerability\r\n \r\nSQL injection in Joomla extension \"DT Register\" by DTH Development\r\nallows remote unauthenticated attacker to execute arbitrary SQL\r\ncommands via the cat parameter.\r\n \r\n \r\n# Preconditions\r\n \r\nNo pre-conditions for authentication or authorization.\r\n \r\n \r\n# Proof-of-Concept\r\n \r\nhttp://[DOMAIN]/[PATH]/index.php?controller=calendar&format=raw&cat[0]=SQLi&task=events\r\n \r\nPoC value (shows out all events / it's possible to see valid eventId values):\r\ncat[0]=6) OR 1-- -\r\n \r\n \r\n## Using UNION\r\n \r\nFor reading the data out using UNION it's important to have and to\r\nknow one valid eventId (detected in previous step).\r\n \r\nIn total there are 112 fields in select query, eventId position is no\r\n13. For output is best to use position 112.\r\n \r\nStep-by-Step - how to read the data out is available in blog:\r\nhttps://security.elarlang.eu/sql-injection-in-joomla-extension-dt-register.html\r\n \r\n \r\n# Vulnerability Disclosure Timeline\r\n \r\nFull communication is available in blog:\r\nhttps://security.elarlang.eu/sql-injection-in-joomla-extension-dt-register.html\r\n \r\n2016-10-17 | me > DTH | via web form - I would like to report some\r\nsecurity holes. What is the correct way for that?\r\n2016-10-18 | me > DTH | any response?\r\n2016-10-25 | me > DTH | mail to [email\u00a0protected]\r\n2016-10-25 | DTH > me |\r\n* \"you are not in our client list\"\r\n* \"Our site (dthdevelopment.com) is protected by an enterprise grade firewall\"\r\n2016-10-25 | me > DTH | I'm whitehat, technical details\r\n2016-10-25 | DTH > me | description, what kind of serious problems I may face\r\n2016-10-25 | me > DTH | explanations\r\n2016-11-02 | me > DTH | hello?\r\n2016-11-11 | me > DTH, SiteLock | Last call.\r\n2016-11-11 | SiteLock / DTH / me | some communication\r\n2016-11-12 | DTH > SiteLock (CC to me) | \"It was configured to be open\r\nin the setup\"\r\n2016-11-15 | DTH | Released DT Register version 3.1.12 (J3.x) / 2.8.18 (J2.5)\r\n2016-12-05 | DTH > me | \"Sorry, forgot to respont on this. We closed\r\nthe problem on our demo site\".\r\n2016-12-12 | me | Full Disclosure on security.elarlang.eu\r\n2016-12-13 | me | Full Disclosure on FullDisclosure mailinglist on seclists.org\r\n \r\n \r\n## asking CVE from DWF (Distributed Weakness Filing Project) /\r\nhttp://iwantacve.org\r\n \r\n2016-10-20 | me > DWF | CVE request\r\n2016-10-31 | DWF > me | \"CVE - Acceptance of MITRE Terms of Use for\r\nCVE Assignment\"\r\n2016-10-31 | me > DWF | I accept\r\n2016-11-19 | me > DWF | Any feedback or decision? (still no response)\r\n2016-12-11 | me > DWF | Is there any hope to get feedback? (still no response)\r\n \r\nAs I haven't got any feedback, you can take this post as CVE request.\r\n \r\n \r\n# Fix\r\nDT Register version 3.1.12 (J3.x) / 2.8.18 (J2.5).\n\n# 0day.today [2018-04-12] #"}