{"answers":{"affected":"2 open source packages ship an affected version, including mogodb.","exploited":"There is no known exploitation of GHSA-w3pp-wp5v-fjvp in the wild and no public exploit code.","fix":"No fix has been published for GHSA-w3pp-wp5v-fjvp yet. Limit exposure of the affected software until one is available.","what":"GHSA-w3pp-wp5v-fjvp is a vulnerability in mogodb, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-w3pp-wp5v-fjvp and fix it if it is affected.\n\nWhat it is: GHSA-w3pp-wp5v-fjvp is a vulnerability in mogodb, published on 3 Sep 2020. 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-w3pp-wp5v-fjvp in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mogodb (npm): affected from 0.0.0; no fix listed\n- mogodb (npm): affected from 0.0.0; no fix listed\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-w3pp-wp5v-fjvp/ (Markdown: https://insights.sbomify.com/GHSA-w3pp-wp5v-fjvp/index.md)","id":"GHSA-w3pp-wp5v-fjvp","markdown":"https://insights.sbomify.com/GHSA-w3pp-wp5v-fjvp/index.md","name":"GHSA-w3pp-wp5v-fjvp","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"workaround","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"npm package","requires_auth":"none","summary":"A malicious npm package exfiltrates system information to a remote server, requiring immediate removal from the environment.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.\n\n## Recommendation\n\nRemove the package from your environment. There are no indications of further compromise.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Malicious Package in mogodb","id":"GHSA-w3pp-wp5v-fjvp","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"supply_chain","year":"2020"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0.0.0"],"last_affected":[],"package":"mogodb","purl":null,"source":"GHSA-w3pp-wp5v-fjvp"},{"ecosystem":"npm","fixed":[],"introduced":["0.0.0"],"last_affected":[],"package":"mogodb","purl":"pkg:npm/mogodb","source":"GHSA-w3pp-wp5v-fjvp"}],"products":null,"published":"2020-09-03","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":"A malicious npm package exfiltrates system information to a remote server, requiring immediate removal from the environment.","url":"https://insights.sbomify.com/GHSA-w3pp-wp5v-fjvp/"}