You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was going through blint SBOM output generated from an apk, However I don't see any useful info which can be used to detected vulnerabilities. Let's say If I get a package name & version then I can look into different vuln DBs to see if its vulnerable. But here in this case none of the returned packages has proper version names or proper lib names.
I understand, since we're decompiling an app and then doing this analysis, so it won't be possible to make fully accurate SBOM (in terms of proper deps/version) But how to use SBOM generated by BLINT to identify vulns?
I can see these kind of details in SBOM, but just wanted to check if this purl is of any use?
@phoenix-patrick Good question! A confidence value of 0.5 indicates the lower confidence the tool has about the purl it came up with. We are working on a symbols database called blint-db, which blint can use to improve the purl matching and the overall confidence.
The plan is to make the source code available with a sample database for top packages. Users can then utilize these to create and maintain their own custom lookup databases.
Hi Team,
I was going through blint SBOM output generated from an apk, However I don't see any useful info which can be used to detected vulnerabilities. Let's say If I get a package name & version then I can look into different vuln DBs to see if its vulnerable. But here in this case none of the returned packages has proper version names or proper lib names.
I understand, since we're decompiling an app and then doing this analysis, so it won't be possible to make fully accurate SBOM (in terms of proper deps/version) But how to use SBOM generated by BLINT to identify vulns?
I can see these kind of details in SBOM, but just wanted to check if this
purl
is of any use?The text was updated successfully, but these errors were encountered: