chore: upgrade swing-kit to 2.3.0 [skip ci] (#6977) (CP: 24.4)

[vaadin-bot]

No description provided.

[github-actions]

Dependencies Report

• 🟠 Known Vulnerabilities:

  • Vulnerabilities in: pkg:npm/[email protected] [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:npm/[email protected] [CVE-2024-45296] (osv-scan)
    👌 From vaadin-rounte:1.7.5. Very low impact for us since we're only running that code in the user's browser and the only impact is a degraded performance.
    ·
  • Vulnerabilities in: pkg:maven/com.fasterxml.jackson.core/[email protected] [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::::::::

• 🚫 Vulnerabilities:

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

• 📔 No License Issues

[Click for more Details]