{"answers":{"affected":"2 open source packages ship an affected version, including yetiforce/yetiforce-crm. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-49508 in the wild and no public exploit code.","fix":"Upgrade yetiforce/yetiforce-crm to 6.5.0 or later.","what":"CVE-2023-49508 is a medium-severity path traversal vulnerability in n/a, published on 16 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-49508 and fix it if it is affected.\n\nWhat it is: CVE-2023-49508 is a medium-severity path traversal vulnerability in n/a, published on 16 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-49508 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- yetiforce/yetiforce-crm (Packagist): affected all versions; fixed in 6.5.0\n- yetiforce/yetiforce-crm (Packagist): affected all versions; fixed in 6.5.0\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-2023-49508/ (Markdown: https://insights.sbomify.com/CVE-2023-49508/index.md)","id":"CVE-2023-49508","markdown":"https://insights.sbomify.com/CVE-2023-49508/index.md","name":"CVE-2023-49508","record":{"aliases":["GHSA-394m-vxwj-363j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"YetiForce CRM","requires_auth":"low_privilege","summary":"Remote authenticated attackers can exploit a directory traversal flaw in YetiForce CRM to access sensitive information via the license parameter.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yetiforce_customer_relationship_management","vendor":"yetiforce"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Directory Traversal vulnerability in YetiForceCompany YetiForceCRM versions 6.4.0 and before allows a remote authenticated attacker to obtain sensitive information via the license parameter in the LibraryLicense.php component.","ecosystems":["Packagist"],"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":"YetiForceCRM Directory Traversal vulnerability","id":"CVE-2023-49508","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":2,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2023-49515"},"packages":[{"ecosystem":"Packagist","fixed":["6.5.0"],"introduced":["0"],"last_affected":[],"package":"yetiforce/yetiforce-crm","purl":null,"source":"GHSA-394m-vxwj-363j"},{"ecosystem":"Packagist","fixed":["6.5.0"],"introduced":["0"],"last_affected":[],"package":"yetiforce/yetiforce-crm","purl":"pkg:composer/yetiforce/yetiforce-crm","source":"GHSA-394m-vxwj-363j"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2023-49502"},"products":["n/a"],"published":"2024-02-16","related":[{"cvss_score":9.1,"headline":"Unrestructed file upload in yetiforcecompany/yetiforcecrm","id":"CVE-2022-1411","kev_date_added":null,"published":"2022-05-05"},{"cvss_score":9,"headline":"Cross-site Scripting (XSS) - Stored in yetiforcecompany/yetiforcecrm","id":"CVE-2022-2890","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":8.8,"headline":"Cross-site Scripting (XSS) - Stored in yetiforcecompany/yetiforcecrm","id":"CVE-2022-2829","kev_date_added":null,"published":"2022-08-23"},{"cvss_score":8,"headline":"Cross-Site Request Forgery (CSRF) in yetiforcecompany/yetiforcecrm","id":"CVE-2022-0269","kev_date_added":null,"published":"2022-01-24"},{"cvss_score":7.7,"headline":"Business Logic Errors in yetiforcecompany/yetiforcecrm","id":"CVE-2021-4117","kev_date_added":null,"published":"2021-12-15"},{"cvss_score":7.3,"headline":"Business Logic Errors in yetiforcecompany/yetiforcecrm","id":"CVE-2021-4111","kev_date_added":null,"published":"2021-12-15"},{"cvss_score":7.1,"headline":"Cross-site Scripting (XSS) - Stored in yetiforcecompany/yetiforcecrm","id":"CVE-2022-2924","kev_date_added":null,"published":"2022-09-20"}],"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":"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-27","vendors":["n/a"]},"summary":"Remote authenticated attackers can exploit a directory traversal flaw in YetiForce CRM to access sensitive information via the license parameter.","url":"https://insights.sbomify.com/CVE-2023-49508/"}