{"answers":{"affected":"2 open source packages ship an affected version, including com.vaadin:vaadin-server.","exploited":"There is no known exploitation of GHSA-j23j-q57m-63v3 in the wild and no public exploit code.","fix":"Upgrade com.vaadin:vaadin-server to 8.14.1 or later.","what":"GHSA-j23j-q57m-63v3 is a denial of service vulnerability in com.vaadin:vaadin-server, published on 13 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-j23j-q57m-63v3 and fix it if it is affected.\n\nWhat it is: GHSA-j23j-q57m-63v3 is a denial of service vulnerability in com.vaadin:vaadin-server, published on 13 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-j23j-q57m-63v3 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.vaadin:vaadin-server (Maven): affected from 8.0.0; fixed in 8.14.1\n- com.vaadin:vaadin-server (Maven): affected from 8.0.0; fixed in 8.14.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-j23j-q57m-63v3/ (Markdown: https://insights.sbomify.com/GHSA-j23j-q57m-63v3/index.md)","id":"GHSA-j23j-q57m-63v3","markdown":"https://insights.sbomify.com/GHSA-j23j-q57m-63v3/index.md","name":"GHSA-j23j-q57m-63v3","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Vaadin Java library","requires_auth":"low_privilege","summary":"An authenticated attacker can cause heap exhaustion and denial of service by requesting excessive data rows in the Vaadin DataCommunicator class.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Missing check in `DataCommunicator` class in `com.vaadin:vaadin-server` versions 8.0.0 through 8.14.0 (Vaadin 8.0.0 through 8.14.0) allows authenticated network attacker to cause heap exhaustion by requesting too many rows of data.","ecosystems":["Maven"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Denial of service in DataCommunicator class in Vaadin 8","id":"GHSA-j23j-q57m-63v3","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Maven","product":null,"products":[],"type":"denial_of_service","year":"2021"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Maven","fixed":["8.14.1"],"introduced":["8.0.0"],"last_affected":[],"package":"com.vaadin:vaadin-server","purl":null,"source":"GHSA-j23j-q57m-63v3"},{"ecosystem":"Maven","fixed":["8.14.1"],"introduced":["8.0.0"],"last_affected":[],"package":"com.vaadin:vaadin-server","purl":"pkg:maven/com.vaadin/vaadin-server","source":"GHSA-j23j-q57m-63v3"}],"products":null,"published":"2021-10-13","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An authenticated attacker can cause heap exhaustion and denial of service by requesting excessive data rows in the Vaadin DataCommunicator class.","url":"https://insights.sbomify.com/GHSA-j23j-q57m-63v3/"}