{"answers":{"affected":"2 open source packages ship an affected version, including Gsemac.Net.","exploited":"There is no known exploitation of GHSA-w4x6-hh3x-wjrx in the wild and no public exploit code.","fix":"Upgrade Gsemac.Net to 0.38.2 or later.","what":"GHSA-w4x6-hh3x-wjrx is a vulnerability in Gsemac.Net, published on 11 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-w4x6-hh3x-wjrx and fix it if it is affected.\n\nWhat it is: GHSA-w4x6-hh3x-wjrx is a vulnerability in Gsemac.Net, published on 11 Dec 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 GHSA-w4x6-hh3x-wjrx in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Gsemac.Net (NuGet): affected all versions; fixed in 0.38.2\n- Gsemac.Net (NuGet): affected all versions; fixed in 0.38.2\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-w4x6-hh3x-wjrx/ (Markdown: https://insights.sbomify.com/GHSA-w4x6-hh3x-wjrx/index.md)","id":"GHSA-w4x6-hh3x-wjrx","markdown":"https://insights.sbomify.com/GHSA-w4x6-hh3x-wjrx/index.md","name":"GHSA-w4x6-hh3x-wjrx","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"NuGet networking library","requires_auth":"none","summary":"Outdated Public Suffix List allows incorrect cookie scoping, potentially exposing user data across domains.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"We have identified that this project contains an out-of-date version of the Public Suffix List (https://publicsuffix.org/). We are carrying out research to identify the potential impacts of using old versions of the Public Suffix List, and we intend to publish our results in academic conferences and journals. Our results will become publicly available after 21 days; this provides time to update your project with an up-to-date version of the Public Suffix List.\n\nGitHub repository: gsemac/Gsemac.Common\nPublic Suffix List path: src/Gsemac.Net/Resources/public_suffix_list.dat\n\nThe Public Suffix List is regularly updated (generally a few times per week), and to ensure that the correct privacy boundaries are maintained between websites, applications that use it should routinely fetch an updated copy. If new suffixes are added to the list, and an old list is then used, privacy boundaries will not be constructed correctly, allowing for data (e.g., cookies) to be set incorrectly, potentially harming privacy.\n\nThere is further guidance on how the Public Suffix List should be used in ICANN’s “Advisory on the Use of Static TLD / Suffix Lists” at https://www.icann.org/en/system/files/files/sac-070-en.pdf.\n\nIf you have any questions about our research, or about usage of the Public Suffix List, please reply via e-mail to [sm@smcquistin.uk](mailto:sm@smcquistin.uk).","ecosystems":["NuGet"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Stale copy of the public suffix list","id":"GHSA-w4x6-hh3x-wjrx","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"NuGet","fixed":["0.38.2"],"introduced":["0"],"last_affected":[],"package":"Gsemac.Net","purl":null,"source":"GHSA-w4x6-hh3x-wjrx"},{"ecosystem":"NuGet","fixed":["0.38.2"],"introduced":["0"],"last_affected":[],"package":"Gsemac.Net","purl":"pkg:nuget/Gsemac.Net","source":"GHSA-w4x6-hh3x-wjrx"}],"products":null,"published":"2023-12-11","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":"Outdated Public Suffix List allows incorrect cookie scoping, potentially exposing user data across domains.","url":"https://insights.sbomify.com/GHSA-w4x6-hh3x-wjrx/"}