{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-48257 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-48257 is a medium-severity vulnerability in n/a, published on 13 Jan 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-2022-48257 and fix it if it is affected.\n\nWhat it is: CVE-2022-48257 is a medium-severity vulnerability in n/a, published on 13 Jan 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-2022-48257 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-2022-48257/ (Markdown: https://insights.sbomify.com/CVE-2022-48257/index.md)","id":"CVE-2022-48257","markdown":"https://insights.sbomify.com/CVE-2022-48257/index.md","name":"CVE-2022-48257","record":{"aliases":["GHSA-9526-g73c-89rr"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Eternal Terminal","requires_auth":"none","summary":"Predictable log file names in /tmp allow attackers to read sensitive information from Eternal Terminal logs.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"eternal_terminal","vendor":"eternal_terminal_project"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"In Eternal Terminal 6.2.1, etserver and etclient have predictable logfile names in /tmp.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2022-48257","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":6,"next":{"headline":"Information disclosure in n/a","id":"CVE-2022-48258"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2022-48256"},"products":["n/a"],"published":"2023-01-13","related":[{"cvss_score":7.5,"headline":"Privilege escalation in Eternal Terminal","id":"CVE-2022-24949","kev_date_added":null,"published":"2022-08-16"},{"cvss_score":7.5,"headline":"Race condition in Eternal Terminal","id":"CVE-2022-24950","kev_date_added":null,"published":"2022-08-16"},{"cvss_score":7,"headline":"Race condition in Eternal Terminal","id":"CVE-2022-24951","kev_date_added":null,"published":"2022-08-16"},{"cvss_score":6.5,"headline":"Several denial of service vulnerabilities exist in Eternal Terminal prior to version 6.2.0, including a DoS triggered remotely by an invalid","id":"CVE-2022-24952","kev_date_added":null,"published":"2022-08-16"},{"cvss_score":6.3,"headline":"Path traversal in n/a","id":"CVE-2023-23558","kev_date_added":null,"published":"2023-02-16"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2022-48258","kev_date_added":null,"published":"2023-01-13"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-04","vendors":["n/a"]},"summary":"Predictable log file names in /tmp allow attackers to read sensitive information from Eternal Terminal logs.","url":"https://insights.sbomify.com/CVE-2022-48257/"}