{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2005-1038 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2005-1038 is a low-severity path traversal vulnerability in Redhat Enterprise Linux, published on 10 Apr 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2005-1038 and fix it if it is affected.\n\nWhat it is: CVE-2005-1038 is a low-severity path traversal vulnerability in Redhat Enterprise Linux, published on 10 Apr 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2005-1038 in the wild and no public exploit code.\n\nAffected product: Redhat Enterprise Linux. 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-2005-1038/ (Markdown: https://insights.sbomify.com/CVE-2005-1038/index.md)","id":"CVE-2005-1038","markdown":"https://insights.sbomify.com/CVE-2005-1038/index.md","name":"CVE-2005-1038","record":{"aliases":["GHSA-xmqm-497m-6h9h","RHSA-2005:361","RHSA-2006:0117"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Vixie cron","requires_auth":"low_privilege","summary":"Local users can read other users' cron files by exploiting symlink handling in the crontab editor.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vixie_cron","vendor":"paul_vixie"},{"product":"enterprise_linux","vendor":"redhat"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"crontab in Vixie cron 4.1, when running with the -e option, allows local users to read the cron files of other users by changing the file being edited to a symlink.  NOTE: there is insufficient information to know whether this is a duplicate of CVE-2001-0235.","ecosystems":["Red Hat:enterprise_linux:3::as","Red Hat:enterprise_linux:3::desktop","Red Hat:enterprise_linux:3::es","Red Hat:enterprise_linux:3::ws","Red Hat:enterprise_linux:4::as","Red Hat:enterprise_linux:4::desktop","Red Hat:enterprise_linux:4::es","Red Hat:enterprise_linux:4::ws"],"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":"Path traversal in n/a","id":"CVE-2005-1038","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"redhat:enterprise_linux","products":["redhat:enterprise_linux"],"type":"path_traversal","year":"2005"},"n_packages":16,"n_references":11,"next":{"headline":"Race condition in n/a","id":"CVE-2005-1039"},"packages":[{"ecosystem":"Red Hat:enterprise_linux:3::as","fixed":["0:4.1-10.EL3"],"introduced":["0"],"last_affected":[],"package":"vixie-cron","purl":"pkg:rpm/redhat/vixie-cron","source":"RHSA-2006:0117"},{"ecosystem":"Red Hat:enterprise_linux:3::as","fixed":["0:4.1-10.EL3"],"introduced":["0"],"last_affected":[],"package":"vixie-cron-debuginfo","purl":"pkg:rpm/redhat/vixie-cron-debuginfo","source":"RHSA-2006:0117"},{"ecosystem":"Red Hat:enterprise_linux:3::desktop","fixed":["0:4.1-10.EL3"],"introduced":["0"],"last_affected":[],"package":"vixie-cron","purl":"pkg:rpm/redhat/vixie-cron","source":"RHSA-2006:0117"},{"ecosystem":"Red Hat:enterprise_linux:3::desktop","fixed":["0:4.1-10.EL3"],"introduced":["0"],"last_affected":[],"package":"vixie-cron-debuginfo","purl":"pkg:rpm/redhat/vixie-cron-debuginfo","source":"RHSA-2006:0117"},{"ecosystem":"Red Hat:enterprise_linux:3::es","fixed":["0:4.1-10.EL3"],"introduced":["0"],"last_affected":[],"package":"vixie-cron","purl":"pkg:rpm/redhat/vixie-cron","source":"RHSA-2006:0117"},{"ecosystem":"Red Hat:enterprise_linux:3::es","fixed":["0:4.1-10.EL3"],"introduced":["0"],"last_affected":[],"package":"vixie-cron-debuginfo","purl":"pkg:rpm/redhat/vixie-cron-debuginfo","source":"RHSA-2006:0117"},{"ecosystem":"Red Hat:enterprise_linux:3::ws","fixed":["0:4.1-10.EL3"],"introduced":["0"],"last_affected":[],"package":"vixie-cron","purl":"pkg:rpm/redhat/vixie-cron","source":"RHSA-2006:0117"},{"ecosystem":"Red Hat:enterprise_linux:3::ws","fixed":["0:4.1-10.EL3"],"introduced":["0"],"last_affected":[],"package":"vixie-cron-debuginfo","purl":"pkg:rpm/redhat/vixie-cron-debuginfo","source":"RHSA-2006:0117"},{"ecosystem":"Red Hat:enterprise_linux:4::as","fixed":["4:4.1-36.EL4"],"introduced":["0"],"last_affected":[],"package":"vixie-cron","purl":"pkg:rpm/redhat/vixie-cron","source":"RHSA-2005:361"},{"ecosystem":"Red Hat:enterprise_linux:4::as","fixed":["4:4.1-36.EL4"],"introduced":["0"],"last_affected":[],"package":"vixie-cron-debuginfo","purl":"pkg:rpm/redhat/vixie-cron-debuginfo","source":"RHSA-2005:361"},{"ecosystem":"Red Hat:enterprise_linux:4::desktop","fixed":["4:4.1-36.EL4"],"introduced":["0"],"last_affected":[],"package":"vixie-cron","purl":"pkg:rpm/redhat/vixie-cron","source":"RHSA-2005:361"},{"ecosystem":"Red Hat:enterprise_linux:4::desktop","fixed":["4:4.1-36.EL4"],"introduced":["0"],"last_affected":[],"package":"vixie-cron-debuginfo","purl":"pkg:rpm/redhat/vixie-cron-debuginfo","source":"RHSA-2005:361"},{"ecosystem":"Red Hat:enterprise_linux:4::es","fixed":["4:4.1-36.EL4"],"introduced":["0"],"last_affected":[],"package":"vixie-cron","purl":"pkg:rpm/redhat/vixie-cron","source":"RHSA-2005:361"},{"ecosystem":"Red Hat:enterprise_linux:4::es","fixed":["4:4.1-36.EL4"],"introduced":["0"],"last_affected":[],"package":"vixie-cron-debuginfo","purl":"pkg:rpm/redhat/vixie-cron-debuginfo","source":"RHSA-2005:361"},{"ecosystem":"Red Hat:enterprise_linux:4::ws","fixed":["4:4.1-36.EL4"],"introduced":["0"],"last_affected":[],"package":"vixie-cron","purl":"pkg:rpm/redhat/vixie-cron","source":"RHSA-2005:361"},{"ecosystem":"Red Hat:enterprise_linux:4::ws","fixed":["4:4.1-36.EL4"],"introduced":["0"],"last_affected":[],"package":"vixie-cron-debuginfo","purl":"pkg:rpm/redhat/vixie-cron-debuginfo","source":"RHSA-2005:361"}],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2005-1037"},"products":["n/a"],"published":"2005-04-10","related":[{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2006-2607","kev_date_added":null,"published":"2006-05-25"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2001-0559","kev_date_added":null,"published":"2002-03-09"},{"cvss_score":4.6,"headline":"Memory corruption in n/a","id":"CVE-2001-0560","kev_date_added":null,"published":"2002-03-09"},{"cvss_score":3.7,"headline":"Race condition in n/a","id":"CVE-2000-1096","kev_date_added":null,"published":"2001-01-22"},{"cvss_score":2.1,"headline":"Misconfiguration in n/a","id":"CVE-2007-1856","kev_date_added":null,"published":"2007-04-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"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-07","vendors":["n/a"]},"summary":"Local users can read other users' cron files by exploiting symlink handling in the crontab editor.","url":"https://insights.sbomify.com/CVE-2005-1038/"}