-
Notifications
You must be signed in to change notification settings - Fork 182
Description
When parsing Nmap XML files with service detection I ran into an interesting scenario: Let's assume I have the following script output in a file:
<script id="http-server-header" output="CerberusFTPServer/11.0"><elem>CerberusFTPServer/11.0</elem></script>
This will result in the following object in the attribute services of NmapHost (NmapService):
{'id': 'http-server-header', 'output': 'CerberusFTPServer/11.0', 'elements': {None: 'CerberusFTPServer/11.0'}}
As the output shows, the key inside elements is None. This may lead to problems when processing the data with other software, i.e. elasticsearch.
In comparison other elements within the XML have a key attribute which seems to be used like here:
<script id="http-methods" output="
 Supported Methods: GET HEAD POST OPTIONS"><table key="Supported Methods"><elem>GET</elem><elem>HEAD</elem><elem>POST</elem><elem>OPTIONS</elem></table></script>
This results in:
{'id': 'http-methods', 'output': '\n Supported Methods: GET HEAD POST OPTIONS', 'elements': {'Supported Methods': {None: ['GET', 'HEAD', 'POST', 'OPTIONS']}}}
(Please note the key inside Supported Methods is also None.)
Tested with libnmap versions 0.7.0 and 0.7.2. Nmap version 7.80.