{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40482 exists.","fix":"No fix has been published for CVE-2022-40482 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-40482 is a medium-severity vulnerability in n/a, published on 25 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-40482 and fix it if it is affected.\n\nWhat it is: CVE-2022-40482 is a medium-severity vulnerability in n/a, published on 25 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40482 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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/CVE-2022-40482/ (Markdown: https://insights.sbomify.com/CVE-2022-40482/index.md)","id":"CVE-2022-40482","markdown":"https://insights.sbomify.com/CVE-2022-40482/index.md","name":"CVE-2022-40482","record":{"aliases":["GHSA-5qxg-5vwh-7j5j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Laravel framework","requires_auth":"none","summary":"Attackers can enumerate valid users in Laravel applications via timing attacks exploiting early returns in authentication logic.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"framework","vendor":"laravel"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"The authentication method in Laravel 8.x through 9.x before 9.32.0 was discovered to be vulnerable to user enumeration via timeless timing attacks with HTTP/2 multiplexing. This is caused by the early return inside the hasValidCredentials method in the Illuminate\\Auth\\SessionGuard class when a user is found to not exist.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2022-40482","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"SQL injection in n/a","id":"CVE-2022-40483"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2022-40480"},"products":["n/a"],"published":"2023-04-25","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2021-43617","kev_date_added":null,"published":"2021-11-14"},{"cvss_score":8.8,"headline":"OS Command Injection in Laravel Framework","id":"CVE-2020-19316","kev_date_added":null,"published":"2021-12-20"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2018-6330","kev_date_added":null,"published":"2019-03-28"},{"cvss_score":8,"headline":"Laravel Reflected XSS via Request Parameter in Debug-Mode Error Page","id":"CVE-2024-13918","kev_date_added":null,"published":"2025-03-10"},{"cvss_score":8,"headline":"Laravel Reflected XSS via Route Parameter in Debug-Mode Error Page","id":"CVE-2024-13919","kev_date_added":null,"published":"2025-03-10"},{"cvss_score":6.9,"headline":"Laravel has a File Validation Bypass","id":"CVE-2025-27515","kev_date_added":null,"published":"2025-03-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-03","vendors":["n/a"]},"summary":"Attackers can enumerate valid users in Laravel applications via timing attacks exploiting early returns in authentication logic.","url":"https://insights.sbomify.com/CVE-2022-40482/"}