{"answers":{"affected":"3 open source packages ship an affected version, including loguru. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-0338 in the wild and no public exploit code.","fix":"Upgrade loguru to 0.5.3 or later.","what":"CVE-2022-0338 is a medium-severity vulnerability in delgan/loguru, published on 25 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-0338 and fix it if it is affected.\n\nWhat it is: CVE-2022-0338 is a medium-severity vulnerability in delgan/loguru, published on 25 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-0338 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- loguru (PyPI): affected all versions; fixed in 0.5.3\n- loguru (PyPI): affected all versions; fixed in 0.5.3\n- loguru (PyPI): affected all versions; fixed in 0.5.3\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-0338/ (Markdown: https://insights.sbomify.com/CVE-2022-0338/index.md)","id":"CVE-2022-0338","markdown":"https://insights.sbomify.com/CVE-2022-0338/index.md","name":"CVE-2022-0338","record":{"aliases":["DEBIAN-CVE-2022-0338","GHSA-39ph-wr67-j4xq","PYSEC-2022-14","UBUNTU-CVE-2022-0338"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python logging library","requires_auth":"low_privilege","summary":"Attackers can access sensitive information stored in log files generated by the loguru Python library.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntrdev","cpe":[{"product":"loguru","vendor":"loguru_project"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Insertion of Sensitive Information into Log File in Conda loguru prior to 0.5.3.","ecosystems":["PyPI"],"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":"Insertion of Sensitive Information into Log File in delgan/loguru","id":"CVE-2022-0338","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":3,"n_references":2,"next":{"headline":"Server-Side Request Forgery (SSRF) in janeczku/calibre-web","id":"CVE-2022-0339"},"packages":[{"ecosystem":"PyPI","fixed":["0.5.3"],"introduced":["0"],"last_affected":[],"package":"loguru","purl":null,"source":"GHSA-39ph-wr67-j4xq"},{"ecosystem":"PyPI","fixed":["0.5.3"],"introduced":["0"],"last_affected":[],"package":"loguru","purl":"pkg:pypi/loguru","source":"GHSA-39ph-wr67-j4xq"},{"ecosystem":"PyPI","fixed":["0.5.3"],"introduced":["0"],"last_affected":[],"package":"loguru","purl":"pkg:pypi/loguru","source":"PYSEC-2022-14"}],"prev":{"headline":"Information disclosure in Chrome","id":"CVE-2022-0337"},"products":["delgan/loguru"],"published":"2022-01-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["delgan"]},"summary":"Attackers can access sensitive information stored in log files generated by the loguru Python library.","url":"https://insights.sbomify.com/CVE-2022-0338/"}