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

Issue #1834 - Fix for High Severity CVE's in karate-core #1869

Merged
merged 2 commits into from
Dec 17, 2021

Conversation

packleader
Copy link
Contributor

Description

  • Relevant Issues : High CVE's Present in karate-core #1834
  • Relevant PRs : (optional)
  • Type of change :
    • New feature
    • Bug fix for existing feature
    • Code quality improvement
    • Addition or Improvement of tests
    • Addition or Improvement of documentation

Another high-severity CVE was found in armeria so I upgraded from 1.13.2 to 1.13.4.

I added dependency-check-maven to the root POM so that dependencies all modules will be checked for CVE's. When doing a build, the check will run during the verify phase, and the aggregate report will be written to target/dependency-check-report.html.

The dependency check plugin has an option to fail the build if any high-severity CVE's are found. I decided to turn that option off as I believe it will make the build too brittle. This means that a manual review of target/dependency-check-report.html is required to see if any vulnerabilities are present.

The report currently shows high-severity CVS's in karate-gatling, karate-demo, and karate-robot. While it would be nice to address those in the future, I believe we can leave them for now since those modules are not shaded.

@packleader
Copy link
Contributor Author

Hm, it builds fine locally. I can see that the Dependency Checker is failing, but I'm not sure why...

@ptrthomas ptrthomas merged commit 850d2a3 into karatelabs:develop Dec 17, 2021
@packleader packleader deleted the bugfix-1834-cve branch January 3, 2022 01:00
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.

None yet

2 participants