Update flow to 24.5.11

[vaadin-bot]

No description provided.

[github-actions]

Dependencies Report

• 🚫 Vulnerabilities:

  • Vulnerabilities in: pkg:maven/ch.qos.logback/logback-core@1.5.12 [CVE-2024-12801, CVE-2024-12798] (osv-scan,owasp)
    · cpe:2.3:a:ch.qos.logback:logback-core:1.5.12:::::::*
  • Vulnerabilities in: pkg:maven/org.springframework.security/spring-security-core@6.3.3 [CVE-2024-38827] (osv-scan)
    ·
  • 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:::::::*
  • Vulnerabilities in: pkg:npm/libxmljs2@0.35.0 [CVE-2024-34394] (osv-scan)
    👌 This is coming from the tools, @cyclonedx/cyclonedx, we have used for sbom module, FP for us.
    ·

• 🟠 Known Vulnerabilities:

  • 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 License Issues

• 🟠 Changes in 24.5-SNAPSHOT since V24.5.9

  • 16 packages removed (16 external, 0 vaadin)
  • 63 packages added (63 external, 0 vaadin)
  • 137 packages modified (56 external, 81 vaadin)
  • 887 packages same (747 external, 140 vaadin)

[Click for more Details]