{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-15272 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-15272 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-15272 is a medium-severity vulnerability in n/a, published on 15 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-15272 and fix it if it is affected.\n\nWhat it is: CVE-2017-15272 is a medium-severity vulnerability in n/a, published on 15 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-15272 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-2017-15272/ (Markdown: https://insights.sbomify.com/CVE-2017-15272/index.md)","id":"CVE-2017-15272","markdown":"https://insights.sbomify.com/CVE-2017-15272/index.md","name":"CVE-2017-15272","record":{"aliases":["GHSA-jc82-2cpg-hfg5"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PSFTPd FTP server","requires_auth":"low_privilege","summary":"Attackers can extract cleartext user passwords from the PSFTPd configuration file due to hardcoded encryption keys and lack of password protection.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"psftpd","vendor":"psftp"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"The PSFTPd 10.0.4 Build 729 server stores its configuration inside PSFTPd.dat. This file is a Microsoft Access Database and can be extracted. The application sets the encrypt flag with the password \"ITsILLEGAL\"; however, this password is not required to extract the data. Cleartext is used for a user password.","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-2017-15272","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-15273"},"packages":[],"prev":{"headline":"Use after free in n/a","id":"CVE-2017-15271"},"products":["n/a"],"published":"2017-11-15","related":[{"cvss_score":5.9,"headline":"Use after free in n/a","id":"CVE-2017-15271","kev_date_added":null,"published":"2017-11-15"},{"cvss_score":5.3,"headline":"Other in n/a","id":"CVE-2017-15270","kev_date_added":null,"published":"2017-11-15"},{"cvss_score":4.3,"headline":"Server-side request forgery in n/a","id":"CVE-2017-15269","kev_date_added":null,"published":"2017-11-15"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can extract cleartext user passwords from the PSFTPd configuration file due to hardcoded encryption keys and lack of password protection.","url":"https://insights.sbomify.com/CVE-2017-15272/"}