{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-6745 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-6745 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-6745 is a medium-severity vulnerability in n/a, published on 31 Aug 2015. 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-2015-6745 and fix it if it is affected.\n\nWhat it is: CVE-2015-6745 is a medium-severity vulnerability in n/a, published on 31 Aug 2015. 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-2015-6745 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-2015-6745/ (Markdown: https://insights.sbomify.com/CVE-2015-6745/index.md)","id":"CVE-2015-6745","markdown":"https://insights.sbomify.com/CVE-2015-6745/index.md","name":"CVE-2015-6745","record":{"aliases":["GHSA-fx44-vv59-vq78"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Banking software","requires_auth":"low_privilege","summary":"Local users can bypass account locking in Basware Banking by deleting entries from the locking table, circumventing security controls.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"banking","vendor":"basware"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Basware Banking (Maksuliikenne) 8.90.07.X relies on the client to enforce account locking, which allows local users to bypass that security mechanism by deleting the entry from the locking table.  NOTE: this identifier was SPLIT from CVE-2015-0942 per ADT2 and ADT3 due to different vulnerability type and different affected versions.  NOTE: this vulnerability exists because of an incorrect fix for CVE-2015-6744.","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":"Security feature bypass in n/a","id":"CVE-2015-6745","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2015"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2015-6746"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2015-6744"},"products":["n/a"],"published":"2015-08-31","related":[{"cvss_score":6.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2015-6742","kev_date_added":null,"published":"2015-08-31"},{"cvss_score":6.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2015-6743","kev_date_added":null,"published":"2015-08-31"},{"cvss_score":5.8,"headline":"Weak cryptography in n/a","id":"CVE-2015-0943","kev_date_added":null,"published":"2015-08-31"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2015-6747","kev_date_added":null,"published":"2015-08-31"},{"cvss_score":4.3,"headline":"Security feature bypass in n/a","id":"CVE-2015-6744","kev_date_added":null,"published":"2015-08-31"},{"cvss_score":2.1,"headline":"Information disclosure in n/a","id":"CVE-2015-6746","kev_date_added":null,"published":"2015-08-31"}],"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-06","vendors":["n/a"]},"summary":"Local users can bypass account locking in Basware Banking by deleting entries from the locking table, circumventing security controls.","url":"https://insights.sbomify.com/CVE-2015-6745/"}