Added project for Vaadin core SBOM checks

[edler-san]

Run via ./scripts/checkCoreLicenses from the root folder.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Dependencies Report

• 🚫 Vulnerabilities:

  • Vulnerabilities in: pkg:maven/org.springframework.security/spring-security-web@6.3.3 [CVE-2024-38821] (osv-scan,owasp)
    · cpe:2.3:a:org.springframework.security:spring-security-web:6.3.3:::::::*

• 🟠 Known Vulnerabilities:

  • Vulnerabilities in: pkg:npm/libxmljs2@0.33.0 [CVE-2024-34394, CVE-2024-34393] (osv-scan)
    👌 This is coming from the tools, @cyclonedx/cyclonedx, we have used for sbom module, FP for us.
    ·
  • Vulnerabilities in: pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.15.3 [CVE-2023-35116] (owasp)
    👌 Not a valid CVE report based on the vendor analysis and research
    · cpe:2.3:a:fasterxml:jackson-databind::::::::
  • Vulnerabilities in: pkg:maven/me.friwi/jcef-api@jcef-99c2f7a%2Bcef-127.3.1%2Bg6cbb30e%2Bchromium-127.0.6533.100 [CVE-2024-21639, CVE-2024-21640] (owasp)
    👌 Wait for the update from the jcefmaven community. Meanwhile the swing-kit is supposed to be used with fixed websites and not to browse the internet, we have a check for that, so the only possible attacker would be the same person that created the swing application, aka our customer devs. so this vulnerability is not classified by us as critical issue
    · cpe:2.3:a:chromiumembedded:chromium_embedded_framework::::::::

• 📔 No Core License Issues

• 📔 No License Issues

• 🟠 Changes in 24.6-SNAPSHOT since V24.6.0.alpha3

  • 67 packages modified (51 external, 16 vaadin)
  • 963 packages same (754 external, 209 vaadin)

[Click for more Details]