Summary
Let's investigate the work required to add the vulnerable software versions modules use in their check methods (and elsewhere) into the module metadata and how we can utilise that to enhance things like the MCP server.
Basic example
In the metadata section of a module we could have a section like
VulnerableVersions => [
{'min': 1.2.3, max: '1.2.5'},
{'min': 2.2.3, max: '2.2.9'} # Optional have multiple ranges
]
Motivation
We can have generic vulnerability checks if we can get the version number reducing duplicate code across modules and then we'd have the metadata available for other use cases such as the RPC and MCP server and search
Summary
Let's investigate the work required to add the vulnerable software versions modules use in their check methods (and elsewhere) into the module metadata and how we can utilise that to enhance things like the MCP server.
Basic example
In the metadata section of a module we could have a section like
Motivation
We can have generic vulnerability checks if we can get the version number reducing duplicate code across modules and then we'd have the metadata available for other use cases such as the RPC and MCP server and search