Is web GUI authentication necessary to exploit CVE-2018-5795 described in VN 2018-003?

  • 0
  • 2
  • Question
  • Updated 2 months ago
  • Answered
In the VN 2018-003 disclosure, it is unclear to me if the attacker would have to be authenticated within the web GUI (as an administrator or otherwise) in order to conduct the arbitrary file write from CVE-2018-5795.  Can you please let me know what your investigation found on this?
Photo of Judd

Judd

  • 102 Points 100 badge 2x thumb

Posted 2 months ago

  • 0
  • 2
Photo of Ondrej Lepa

Ondrej Lepa, Employee

  • 5,638 Points 5k badge 2x thumb
Hello Judd,

as per the VN description I assume attacker does NOT have to be authenticated

Following are the noted vulnerabilities:

  • Remote and unauthenticated XML entity expansion vulnerability can cause denial of service (CVE-2018-5789)CVSS base score: 7.5 (High) (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
  • Arbitrary file write from WebGUI (CVE-2018-5795)CVSS base score: 2.6 (Low) (CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:L/A:N)
Attack: To launch this attack, a malicious user needs access to the management interface of the WiNG AP / Controller. An attack consists of sending specially crafted XML entities that could lead to AP / Controller crash

That is why we recommend to restrict access to WiNG device using an internal subnet, IP or ACL.

Regards,
Ondrej
Photo of Judd

Judd

  • 102 Points 100 badge 2x thumb
Thank you for the response, I was attempting to NOT have to make assumptions.  You understand my confusion given the difference in wording between the two CVEs.  Did the team doing analysis of the IOActive research CONFIRM no GUI authentication is necessary?

Restricting GUI access via ACL is a given, however it only reduces the attack surface.  ACL + strong GUI password policy would be better... if the authentication matters.
Photo of Judd

Judd

  • 102 Points 100 badge 2x thumb
In case others are watching this, the release notes claiming fix for CVE-2018-5795 indicates low access authentication is required for this particular CVE.

https://documentation.extremenetworks.com/release_notes/WiNG/9035206-03_WiNG%205_9_1_3%20Release_Not...