{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2014-4810 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-4810 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-4810 is a medium-severity authentication bypass vulnerability in n/a, published on 5 Nov 2014. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2014-4810 and fix it if it is affected.\n\nWhat it is: CVE-2014-4810 is a medium-severity authentication bypass vulnerability in n/a, published on 5 Nov 2014. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2014-4810 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-4810/ (Markdown: https://insights.sbomify.com/CVE-2014-4810/index.md)","id":"CVE-2014-4810","markdown":"https://insights.sbomify.com/CVE-2014-4810/index.md","name":"CVE-2014-4810","record":{"aliases":["GHSA-vcxp-3rhh-fwg2"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Cognos Mobile","requires_auth":"low_privilege","summary":"Attackers can bypass Business Intelligence restrictions by leveraging captured authentication data from sessions that persist after mobile logoff.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"cognos_mobile","vendor":"ibm"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"IBM Cognos Mobile 10.1.1 before FP3 IF1, 10.2.0 before FP2 IF1, and 10.2.1 before FP4 IF1 preserves a session between the Cognos Mobile server and the Cognos Business Intelligence server after a logoff action on a mobile device, which makes it easier for remote attackers to bypass intended Business Intelligence restrictions by leveraging access to authentication data that was captured before this logoff.","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":"Auth bypass in n/a","id":"CVE-2014-4810","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2014"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2014-4811"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2014-4809"},"products":["n/a"],"published":"2014-11-05","related":[],"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":"Attackers can bypass Business Intelligence restrictions by leveraging captured authentication data from sessions that persist after mobile logoff.","url":"https://insights.sbomify.com/CVE-2014-4810/"}