Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix wrong values in snmp_sysdescr.xml #286

Merged
merged 4 commits into from
Sep 9, 2020

Conversation

nstylepro
Copy link
Contributor

Changed wrong values of 2 fingerprints

@hdm
Copy link
Contributor

hdm commented Aug 30, 2020

👍 LGTM

@tsellers-r7
Copy link
Contributor

Thanks for the contribution. We don't currently have anything else that uses os.device of HMI Controller. Keeping in mind that os.device is a generic classification for the device, what's the value of adding the specificity here? Is this a label we should apply to other fingerprints?

@tsellers-r7
Copy link
Contributor

As a note, I see that it is listed in https://github.com/rapid7/recog/blob/master/identifiers/hw_device.txt and that we have one occurrence of it's use;

recog/xml/html_title.xml

Lines 1316 to 1325 in c0deef7

<fingerprint pattern="^(1747-\S+) Home Page$">
<description>Allen-Bradley 1747-LXXX SLC 5/05 Controller</description>
<example hw.product="1747-L551">1747-L551 Home Page</example>
<example hw.product="1747-L551/C">1747-L551/C Home Page</example>
<example hw.product="1747-L552/C">1747-L552/C Home Page</example>
<param pos="0" name="hw.vendor" value="Allen-Bradley"/>
<param pos="0" name="hw.device" value="HMI Controller"/>
<param pos="1" name="hw.product"/>
<param pos="0" name="os.vendor" value="Allen-Bradley"/>
</fingerprint>

@nstylepro
Copy link
Contributor Author

well, that's incorrect. there is this one:

<fingerprint pattern="^(1747-\S+) Home Page$">

the specificity is not so important, but Monitoring is not the proper classification for HMI devices, while they are usually old Windows box

@tsellers-r7
Copy link
Contributor

I made a comment on that one about a split second before you did. Make sense, particularly if this is a firmware image and not stock Windows with some service running on it. This seems like it'd be a good time to had hw.* fields as well since it appears that Siemens makes these and the banner contains model information. Does that sound correct?

If it is correct I can follow this up with a PR to add them if needed.

@nstylepro
Copy link
Contributor Author

Sound like a good Idea.

@nstylepro
Copy link
Contributor Author

nstylepro commented Sep 1, 2020

actually did some further research on these devices. turned out this is running WindowsCE!
(not )
https://support.industry.siemens.com/cs/images/thumbnails/28263711/protool_image_versionen_01_e.gif

should fix that as well. LMK if you want me to push the change as well.

e.g. here:

<param pos="0" name="os.family" value="Simatic HMI"/>

actually os.family correct mapping will be
Simatic HMI -> should be WindowsCE
Simatic NET -> should be Windows7
Simatic S7 -> should be Windows
Simatic Sinumerikare -> should be Windows10
and not OSs. they are software on top of some Windows.

@tsellers-r7
Copy link
Contributor

@nstylepro - Yes, if you could add these changes that'd be great. Thanks!

@nstylepro
Copy link
Contributor Author

@nstylepro - Yes, if you could add these changes that'd be great. Thanks!

review again :)

@@ -6318,10 +6318,12 @@ Copyright (c) 1995-2005 by Cisco Systems
<example>Siemens, SIMATIC HMI, KTP600 Basic Mono PN, 6AV6647-0AB11-3AX0, HW:1, FW:V01.06.00</example>
<example>Siemens, SIMATIC HMI, KTP600 Basic color PN, 6AV6 647-0AD11-3AX0, HW:1, FW:V11.00.02.00</example>
<param pos="0" name="os.vendor" value="Siemens"/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

os.vendor here and elsewhere should be Microsoft.
hw.vendor should, I'm guessing, be Siemens?
Can you group the os.* and hw.* together?

<param pos="2" name="os.version"/>
<param pos="0" name="os.family" value="Windows"/>
<param pos="0" name="hw.family" value="Simatic S7"/>
<param pos="1" name="hw.product"/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes from os.product to hw.product are what broke the tests. You can change the field in the example and retest using rspec

@tsellers-r7
Copy link
Contributor

I'll land this and fix the issues. Thanks much for the feedback and pr @nstylepro

@tsellers-r7 tsellers-r7 merged commit b6889a7 into rapid7:master Sep 9, 2020
@tsellers-r7
Copy link
Contributor

FYI, here is a PR with the changes: #291

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants