{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-1440 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-1440 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1440 is a critical vulnerability in n/a, published on 18 Mar 2003. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2002-1440 and fix it if it is affected.\n\nWhat it is: CVE-2002-1440 is a critical vulnerability in n/a, published on 18 Mar 2003. 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-2002-1440 in the wild and no public exploit code.\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-2002-1440/ (Markdown: https://insights.sbomify.com/CVE-2002-1440/index.md)","id":"CVE-2002-1440","markdown":"https://insights.sbomify.com/CVE-2002-1440/index.md","name":"CVE-2002-1440","record":{"aliases":["GHSA-j7w4-w286-7x9h"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Gateway GS-400 server","requires_auth":"none","summary":"Attackers can gain root privileges on Gateway GS-400 servers using a hardcoded default password that cannot be changed via the admin interface.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gs-400","vendor":"gateway"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"The Gateway GS-400 server has a default root password of \"0001n\" that can not be changed via the administrative interface, which can allow attackers to gain root privileges.","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":"Hardcoded credentials in n/a","id":"CVE-2002-1440","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2002"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2002-1441"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2002-1439"},"products":["n/a"],"published":"2003-03-18","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Attackers can gain root privileges on Gateway GS-400 servers using a hardcoded default password that cannot be changed via the admin interface.","url":"https://insights.sbomify.com/CVE-2002-1440/"}