{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-40182 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-40182 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-40182 is a low-severity vulnerability in mesosoi silverwaregames-io-issue-tracker, published on 25 Aug 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-2023-40182 and fix it if it is affected.\n\nWhat it is: CVE-2023-40182 is a low-severity vulnerability in mesosoi silverwaregames-io-issue-tracker, published on 25 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-40182 in the wild and no public exploit code.\n\nAffected product: mesosoi silverwaregames-io-issue-tracker. 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-2023-40182/ (Markdown: https://insights.sbomify.com/CVE-2023-40182/index.md)","id":"CVE-2023-40182","markdown":"https://insights.sbomify.com/CVE-2023-40182/index.md","name":"CVE-2023-40182","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Silverware Games social network","requires_auth":"none","summary":"An attacker can determine if an email address exists in the database by observing response time differences in the recovery form.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"silverwaregames","vendor":"silverwaregames"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"Silverware Games is a premium social network where people can play games online. When using the Recovery form, a noticeably different amount of time passes depending of whether the specified email address presents in our database or not. This has been fixed in version 1.3.7.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in silverwaregames-io-issue-tracker","id":"CVE-2023-40182","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"DataEase has a vulnerability to obtain user cookies","id":"CVE-2023-40183"},"packages":[],"prev":{"headline":"Integer-Underflow leading to Out-Of-Bound Read in FreeRDP","id":"CVE-2023-40181"},"products":["silverwaregames-io-issue-tracker"],"published":"2023-08-25","related":[{"cvss_score":6.3,"headline":"HTML attributes when attaching a YouTube link to the post","id":"CVE-2022-23543","kev_date_added":null,"published":"2022-12-19"},{"cvss_score":5.9,"headline":"SilverwareGames.io used == for hashing instead of ===","id":"CVE-2022-36072","kev_date_added":null,"published":"2022-09-06"},{"cvss_score":5.3,"headline":"Silverware Games vulnerable to account enumeration via inconsistent responses","id":"CVE-2023-40179","kev_date_added":null,"published":"2023-08-25"},{"cvss_score":2.7,"headline":"Missing authorization in silverwaregames-io-issue-tracker","id":"CVE-2023-29192","kev_date_added":null,"published":"2023-04-10"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-30","vendors":["mesosoi"]},"summary":"An attacker can determine if an email address exists in the database by observing response time differences in the recovery form.","url":"https://insights.sbomify.com/CVE-2023-40182/"}