Add: Add new API for parsing CPEs (pontos.cpe) #913
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allow to parse and analyze CPE information from their v2.2 and v2.3 string representations. It's also possible to convert a v2.2 CPE representation into a v2.3 and vice versa. It follows the spec at https://nvlpubs.nist.gov/nistpubs/Legacy/IR/nistir7695.pdf very closely and implements all their escaping. Just the conversion to percent-encoded strings for quoting non-alphanumeric characters is using `urllib.parser.quote` and `unquote` which support additional quoting besides specified in the CPE document.
Conventional Commits Report
🚀 Conventional commits found. |
Codecov Report
@@ Coverage Diff @@
## main #913 +/- ##
==========================================
+ Coverage 90.18% 90.33% +0.14%
==========================================
Files 94 95 +1
Lines 6366 6588 +222
Branches 900 944 +44
==========================================
+ Hits 5741 5951 +210
- Misses 432 437 +5
- Partials 193 200 +7
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
y0urself
approved these changes
Oct 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Add new API for parsing CPEs (pontos.cpe)
It follows the spec at https://nvlpubs.nist.gov/nistpubs/Legacy/IR/nistir7695.pdf very closely and implements all their escaping. Just the conversion to percent-encoded strings for quoting non-alphanumeric characters is using
urllib.parser.quoteandunquotewhich support additional quoting besides specified in the CPE document.Why
Allow to parse and analyze CPE information from their v2.2 and v2.3 string representations. It's also possible to convert a v2.2 CPE representation into a v2.3 and vice versa. We need this for being able to use the new NIST CVE and CPE API.
References
DEVOPS-472
Checklist