Hello, we discovered that our fleetdm instance rep...
# fleet
f
Hello, we discovered that our fleetdm instance reported a lot of false positive. There is any possibilties to manualy manage cpe translation? Or to manage any other vulnerabilities checker to improve accuracy ?
e.g.
hosts for both are the same.... so im wondering why we got 2 different result for same.
you can see also that fleetdm is not getting version of SQL Server
k
Hey @Filip! What version of Fleet are you running? What other false positives are you running in to?
f
currently we're running latest version 4.36.0. We observing much more false positives. On test host, where we have installed the newest host agent we got more false positives but i based on trust that users really updated software. At this moment im 100 % sure that there is something wrong with sql server vulnerabiility check
Copy code
SoftwareName    : Microsoft SQL Server 2012
SoftwareVersion : 
AffectedUsers   : 2
CVECount        : 101
CPE             : cpe:2.3:a:microsoft:sql_server:*:*:*:*:*:windows:*:*

SoftwareName    : Microsoft SQL Server 2012 (64-bit)
SoftwareVersion : 
AffectedUsers   : 3
CVECount        : 101
CPE             : cpe:2.3:a:microsoft:sql_server:*:*:*:*:*:windows:*:*

SoftwareName    : Microsoft SQL Server 2017
SoftwareVersion : 
AffectedUsers   : 1
CVECount        : 101
CPE             : cpe:2.3:a:microsoft:sql_server:*:*:*:*:*:windows:*:*

SoftwareName    : Microsoft SQL Server 2017 (64-bit)
SoftwareVersion : 
AffectedUsers   : 5
CVECount        : 101
CPE             : cpe:2.3:a:microsoft:sql_server:*:*:*:*:*:windows:*:*

SoftwareName    : Microsoft SQL Server 2019 (64-bit)
SoftwareVersion : 
AffectedUsers   : 70
CVECount        : 101
CPE             : cpe:2.3:a:microsoft:sql_server:*:*:*:*:*:windows:*:*

SoftwareName    : Microsoft SQL Server 2022 (64-bit)
SoftwareVersion : 
AffectedUsers   : 14
CVECount        : 101
CPE             : cpe:2.3:a:microsoft:sql_server:*:*:*:*:*:windows:*:*
k
Any other affected software, or is it all Microsoft SQL Server?
Can you run this query on one of the affected hosts and let me know what you get back? It looks like the underlying issue is that the version isn't coming back properly. This will show us if that's an osquery issue or something in the way we're ingesting software:
Copy code
select name, version from programs where name like "Microsoft SQL Server%";
f
response from one of the affected host
image.png
another false positive :
represented by:
Copy code
cpe:2.3:a:nodejs:node.js:18.17.1:*:*:*:*:windows:*:*
if you go to : CVE-2023-32004
resolve matching cpe i wont find 18.17.1
the only CPE which i found is :
Copy code
cpe:2.3:a:nodejs:node.js:18.0.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.0.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.0.2:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.0.3:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.0.4:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.0.5:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.0.6:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.1.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.2.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.3.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.4.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.5.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.6.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.7.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.8.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.9.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.9.1:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.10.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:18.11.0:*:*:*:-:*:*:*
it look like you are not checking descripted CPE match ?
for teams:
Copy code
cpe:2.3:a:microsoft:teams:1.6.00.22378:*:*:*:*:windows:*:*
in the list there is no matching version
there is a lot more examples for false positives
i wont send all of them because it will last ages 🙂
k
Thanks @Filip. Would you be willing to submit a bug report ticket for this? It definitely looks like there's something amiss. I'd be happy to submit it for you, but you've got access to the information so it seems like a good idea to cut out the middle man :)
f
yes, i will mentioned you into this bug ok ?
@Kathy Satterlee it will be great if you will paricipate in this bug 🙂 https://github.com/fleetdm/fleet/issues/13615
k
Thanks @Filip! I've gotten the intake process going for that and we'll be taking a look at what the root of the issue is so we can fix it. Really appreciate the report... vulnerability processing is tricky.
f
Hi @Kathy Satterlee, do you know any estimated date for this fix release ?
k
It doesn't look like we're scheduled for a release at the moment, the team is still looking in to the root cause of the issue.