CVE-2017-0911

Name: CVE-2017-0911
Creator: NVD / NIST
Published: 2018-02-09T22:29:00.613+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 0.51%

Last modified Jun 17, 2026

CVE-2017-0911 is a vulnerability of currently unknown severity. 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-<consumer-key>) on iOS. EPSS estimates a 0.51% chance of exploitation in the next 30 days.

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-<consumer-key>) 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.

Metrics

EPSS Probability

0.51%

39.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Vendor	Product	Versions
Twitter	Twitter Kit	>= 3.0, <= 3.2.1

References

https://blog.twitter.com/developer/en_us/topics/tips/2018/vulnerability-in-twitter-kit-for-ios.htmlThird Party Advisory
https://github.com/twitter/twitter-kit-ios/blob/b6eb49d149b056d826cbc4b53eaeb39a3ebd591e/TwitterKit/TwitterKit/Social/Identity/TWTRMobileSSO.m#L71Patch, Third Party Advisory
https://github.com/twitter/twitter-kit-ios/blob/b6eb49d149b056d826cbc4b53eaeb39a3ebd591e/TwitterKit/TwitterKit/TWTRTwitter.m#L411Patch, Third Party Advisory
https://github.com/twitter/twitter-kit-ios/wiki/Changelog#322-november-28-2017Release Notes, Third Party Advisory
https://hackerone.com/reports/290229Permissions Required, Third Party Advisory
https://blog.twitter.com/developer/en_us/topics/tips/2018/vulnerability-in-twitter-kit-for-ios.htmlThird Party Advisory
https://github.com/twitter/twitter-kit-ios/blob/b6eb49d149b056d826cbc4b53eaeb39a3ebd591e/TwitterKit/TwitterKit/Social/Identity/TWTRMobileSSO.m#L71Patch, Third Party Advisory
https://github.com/twitter/twitter-kit-ios/blob/b6eb49d149b056d826cbc4b53eaeb39a3ebd591e/TwitterKit/TwitterKit/TWTRTwitter.m#L411Patch, Third Party Advisory
https://github.com/twitter/twitter-kit-ios/wiki/Changelog#322-november-28-2017Release Notes, Third Party Advisory
https://hackerone.com/reports/290229Permissions Required, Third Party Advisory

Timeline

Published: Feb 9, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-0911?

How severe is CVE-2017-0911?

Severity scoring for CVE-2017-0911 is pending analysis. The EPSS model estimates a 0.51% probability of exploitation in the next 30 days.

How do I fix CVE-2017-0911?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-0911?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST