{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-0911 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-0911 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-0911 is a medium-severity authentication bypass vulnerability in Twitter Kit for iOS, published on 9 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-0911 and fix it if it is affected.\n\nWhat it is: CVE-2017-0911 is a medium-severity authentication bypass vulnerability in Twitter Kit for iOS, published on 9 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-0911 in the wild and no public exploit code.\n\nAffected product: Twitter Kit for iOS. 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-0911/ (Markdown: https://insights.sbomify.com/CVE-2017-0911/index.md)","id":"CVE-2017-0911","markdown":"https://insights.sbomify.com/CVE-2017-0911/index.md","name":"CVE-2017-0911","record":{"aliases":["GHSA-rcwq-7c2v-mc74"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Twitter Kit iOS","requires_auth":"low_privilege","summary":"Attackers can forge authentication callbacks to associate Twitter accounts with third-party services due to missing response verification in the login flow.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"twitter_kit","vendor":"twitter"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-360","name":"Trust of System Event Data"}],"description":"Twitter Kit for iOS versions 3.0 to 3.2.1 is vulnerable to a callback verification flaw in the \"Login with Twitter\" component allowing an attacker to provide alternate credentials. In the final step of \"Login with Twitter\" authentication information is passed back to the application using the registered custom URL scheme (typically twitterkit-\u003cconsumer-key\u003e) on iOS. Because the callback handler did not verify the authenticity of the response, this step is vulnerable to forgery, potentially allowing attacker to associate a Twitter account with a third-party 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":false,"headline":"Auth bypass in Twitter Kit for iOS","id":"CVE-2017-0911","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2017"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-0912"},"packages":[],"prev":{"headline":"Missing authorization in Zulip Server","id":"CVE-2017-0910"},"products":["Twitter Kit for iOS"],"published":"2018-02-09","related":[{"cvss_score":7.4,"headline":"Weak cryptography in n/a","id":"CVE-2019-16263","kev_date_added":null,"published":"2019-10-07"},{"cvss_score":5.4,"headline":"Auth bypass in Twitter Kit for iOS","id":"CVE-2019-5431","kev_date_added":null,"published":"2019-05-06"}],"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-09-17","vendors":["Twitter"]},"summary":"Attackers can forge authentication callbacks to associate Twitter accounts with third-party services due to missing response verification in the login flow.","url":"https://insights.sbomify.com/CVE-2017-0911/"}