<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: MSM765 active directory authentication security issue in M and MSM Series</title>
    <link>https://community.hpe.com/t5/m-and-msm-series/msm765-active-directory-authentication-security-issue/m-p/6220733#M2271</link>
    <description>&lt;P&gt;We solved part of the problem by upgrading the software on the msm765 from 5.7 to 6.0.1. After that most students are not connected anymore, showing an authentication failure in the log of the msm765.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, a small number of students is still able to connect with non existing Active Directory accounts like "islam" and "christus". The msm765 shows a "RADIUS authentication OK" message. The students seem to use some sort of app on their smartphone that exploits a vulnerability in either the protocol or the implementation by HP. We are further investigating this. Other option we have is to use a wifi scanner to track down the students. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 29 Sep 2013 08:54:55 GMT</pubDate>
    <dc:creator>Marcel Mossel</dc:creator>
    <dc:date>2013-09-29T08:54:55Z</dc:date>
    <item>
      <title>MSM765 active directory authentication security issue</title>
      <link>https://community.hpe.com/t5/m-and-msm-series/msm765-active-directory-authentication-security-issue/m-p/6203971#M2257</link>
      <description>&lt;P&gt;Our school has a MSM765zl controller. The firmware version is 5.7.0.3-11516. We have found a important security risk concerning the Active Directory authentication.&lt;/P&gt;&lt;P&gt;&amp;nbsp;Users are authenticated via Active Directory. Radius Is not configured. In Active Directory and on the msm765 we have defined several security groups with identical names that determine to which vsc/ssid an user has access. Each user is a member of only 1 group.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cvo-nowifi&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; no wifi access, because the vsc is not available on any AP&lt;/P&gt;&lt;P&gt;Cvo-leerling&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; students&lt;/P&gt;&lt;P&gt;Cvo-mdw&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; employees&lt;/P&gt;&lt;P&gt;Cvo-gast&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; guests&lt;/P&gt;&lt;P&gt;Cvo-edu&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; managed laptops owned by the school&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The default group is restricted to the nowifi vsc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have tested this with a Windows 7 laptop and it works fine. A user has access if he/she is a member of the corresponding AD group and access is denied if he/she is not a member.&lt;/P&gt;&lt;P&gt;However, when we connect from an smartphone (we tested with an Android Phone) &amp;nbsp;we find that one can connect to any vsc. The same issue exist on tablets, since student are able to login to the employee vsc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sofar we were not able to solve this issue so we are thinking of using an alternative solution with only a single vsc/ssid for all users and a dynamically assigned vlan based on group membership.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, using more than one vsc/ssid has certain advantages:&lt;/P&gt;&lt;P&gt;-&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; One can differentiate between different groups with respect to the availability of the wireless network on specific locations;&lt;/P&gt;&lt;P&gt;-&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; It is possible to assign different priorities to different vsc’s;&lt;/P&gt;&lt;P&gt;-&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Since each AP has two transmitters one may limit certain vsc’s to only one frequency band, ensuring a more reliable performance on the other band,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Off course I can use the remote access permission, but then I block access to all ssid’s.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there something we are doing wrong?&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2013 21:58:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/m-and-msm-series/msm765-active-directory-authentication-security-issue/m-p/6203971#M2257</guid>
      <dc:creator>Marcel Mossel</dc:creator>
      <dc:date>2013-09-13T21:58:27Z</dc:date>
    </item>
    <item>
      <title>Re: MSM765 active directory authentication security issue</title>
      <link>https://community.hpe.com/t5/m-and-msm-series/msm765-active-directory-authentication-security-issue/m-p/6220733#M2271</link>
      <description>&lt;P&gt;We solved part of the problem by upgrading the software on the msm765 from 5.7 to 6.0.1. After that most students are not connected anymore, showing an authentication failure in the log of the msm765.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, a small number of students is still able to connect with non existing Active Directory accounts like "islam" and "christus". The msm765 shows a "RADIUS authentication OK" message. The students seem to use some sort of app on their smartphone that exploits a vulnerability in either the protocol or the implementation by HP. We are further investigating this. Other option we have is to use a wifi scanner to track down the students. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 29 Sep 2013 08:54:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/m-and-msm-series/msm765-active-directory-authentication-security-issue/m-p/6220733#M2271</guid>
      <dc:creator>Marcel Mossel</dc:creator>
      <dc:date>2013-09-29T08:54:55Z</dc:date>
    </item>
    <item>
      <title>Re: MSM765 active directory authentication security issue</title>
      <link>https://community.hpe.com/t5/m-and-msm-series/msm765-active-directory-authentication-security-issue/m-p/6404258#M3713</link>
      <description>&lt;P&gt;We already solved this some time ago. We use laptops that authenticate the machine against Active Directory. These laptops are already connected with the wireless network before user logon. With a tool students copy a certain security key from the computer and import this onto their mobiel phone. Two solutions exist:&lt;/P&gt;&lt;P&gt;1 - Use machine certicates;&lt;/P&gt;&lt;P&gt;2 - Block users from reading the security key.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 08 Mar 2014 12:50:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/m-and-msm-series/msm765-active-directory-authentication-security-issue/m-p/6404258#M3713</guid>
      <dc:creator>Marcel Mossel</dc:creator>
      <dc:date>2014-03-08T12:50:12Z</dc:date>
    </item>
  </channel>
</rss>

