{"answers":{"affected":"It affects 7 products.","exploited":"There is no known exploitation of CVE-2004-2048 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2004-2048 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-2048 is a critical vulnerability in n/a, published on 10 May 2005. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2004-2048 and fix it if it is affected.\n\nWhat it is: CVE-2004-2048 is a critical vulnerability in n/a, published on 10 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2004-2048 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-2004-2048/ (Markdown: https://insights.sbomify.com/CVE-2004-2048/index.md)","id":"CVE-2004-2048","markdown":"https://insights.sbomify.com/CVE-2004-2048/index.md","name":"CVE-2004-2048","record":{"aliases":["GHSA-74fr-mmwf-rxrm"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Thintune thin client","requires_auth":"low_privilege","summary":"Remote attackers can gain unauthorized access to eSeSIX Thintune thin clients using a hardcoded default password on port 25072.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"thintune_extreme","vendor":"esesix"},{"product":"thintune_l","vendor":"esesix"},{"product":"thintune_m","vendor":"esesix"},{"product":"thintune_mobile","vendor":"esesix"},{"product":"thintune_s","vendor":"esesix"},{"product":"thintune_xm","vendor":"esesix"},{"product":"thintune_xs","vendor":"esesix"}],"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":"radmin in eSeSIX Thintune thin clients running firmware 2.4.38 and earlier starts a process port 25072 that can be accessed with a default \"jstwo\" password, which allows remote attackers to gain access.","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-2004-2048","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2004"},"n_packages":0,"n_references":6,"next":{"headline":"Information disclosure in n/a","id":"CVE-2004-2049"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2004-2047"},"products":["n/a"],"published":"2005-05-10","related":[{"cvss_score":5,"headline":"Path traversal in n/a","id":"CVE-2004-2051","kev_date_added":null,"published":"2005-05-10"},{"cvss_score":4.6,"headline":"Information disclosure in n/a","id":"CVE-2004-2049","kev_date_added":null,"published":"2005-05-10"},{"cvss_score":4.6,"headline":"Hardcoded credentials in n/a","id":"CVE-2004-2050","kev_date_added":null,"published":"2005-05-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can gain unauthorized access to eSeSIX Thintune thin clients using a hardcoded default password on port 25072.","url":"https://insights.sbomify.com/CVE-2004-2048/"}