{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2014-8309 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-8309 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-8309 is a medium-severity vulnerability in n/a, published on 16 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2014-8309 and fix it if it is affected.\n\nWhat it is: CVE-2014-8309 is a medium-severity vulnerability in n/a, published on 16 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2014-8309 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-2014-8309/ (Markdown: https://insights.sbomify.com/CVE-2014-8309/index.md)","id":"CVE-2014-8309","markdown":"https://insights.sbomify.com/CVE-2014-8309/index.md","name":"CVE-2014-8309","record":{"aliases":["GHSA-q44j-435f-vxcg"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SAP BusinessObjects","requires_auth":"none","summary":"Remote attackers can enumerate valid usernames by analyzing timing differences in failed login responses from the Session web service.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"businessobjects","vendor":"sap"},{"product":"businessobjects_xi","vendor":"sap"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"SAP BusinessObjects 4.0 and BusinessObjects XI (BOXI) R2 and 3.1 generates error messages for a failed logon attempt with different time delays depending on whether the user account exists, which allows remote attackers to enumerate valid usernames via SecEnterprise authentication requests to the Session web service.","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":"Information disclosure in n/a","id":"CVE-2014-8309","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2014"},"n_packages":0,"n_references":7,"next":{"headline":"Denial of service in n/a","id":"CVE-2014-8310"},"packages":[],"prev":{"headline":"Cross-site scripting (XSS) vulnerability in the Send to Inbox functionality in SAP BusinessObjects BI EDGE 4.0 allows remote attackers to in","id":"CVE-2014-8308"},"products":["n/a"],"published":"2014-10-16","related":[{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-2015-7730","kev_date_added":null,"published":"2015-10-15"},{"cvss_score":10,"headline":"Auth bypass in n/a","id":"CVE-2014-9387","kev_date_added":null,"published":"2014-12-17"},{"cvss_score":9.8,"headline":"File upload in SAP BusinessObjects Business Intelligence Platform Servers (Enterprise)","id":"CVE-2019-0259","kev_date_added":null,"published":"2019-02-15"},{"cvss_score":9,"headline":"Privilege escalation in n/a","id":"CVE-2010-3983","kev_date_added":null,"published":"2010-10-18"},{"cvss_score":7.8,"headline":"Information disclosure in SAP BusinessObjects Enterprise (Central Management Server)","id":"CVE-2022-28214","kev_date_added":null,"published":"2022-05-11"},{"cvss_score":7.6,"headline":"Information disclosure in SAP BusinessObjects Business Intelligence platform (Central Management Server)","id":"CVE-2019-0287","kev_date_added":null,"published":"2019-05-14"},{"cvss_score":7.3,"headline":"Security feature bypass in SAP Business Objects","id":"CVE-2018-2408","kev_date_added":null,"published":"2018-04-10"}],"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":"Remote attackers can enumerate valid usernames by analyzing timing differences in failed login responses from the Session web service.","url":"https://insights.sbomify.com/CVE-2014-8309/"}