Which versions of passport-cognito are affected by CVE-2019-19723?

passport-cognito (npm) versions >= 0.0.0 is affected.

Is there a fix for CVE-2019-19723?

No fixed version is listed for CVE-2019-19723 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2019-19723 exploitable, and should I be worried?

Whether CVE-2019-19723 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2019-19723 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2019-19723 in passport-cognito

CVE-2019-19723

CVE-2019-19723 is a critical-severity security vulnerability in passport-cognito (npm), affecting versions >= 0.0.0. No fixed version is listed yet.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Improper Authorization in passport-cognito

All versions of passport-cognito are vulnerable to Improper Authorization. The package fails to properly scope the variables containing authorization information, such as access token, refresh token and ID token. This causes a race condition where simultaneous authenticated users may receive authorization tokens for a different user. This would allow a user to take actions on another user's behalf.

Impact

Affected versions

passport-cognito (>= 0.0.0)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

No fix is currently available. Consider using an alternative package until a fix is made available.

Frequently Asked Questions

What is CVE-2019-19723? CVE-2019-19723 is a critical-severity security vulnerability in passport-cognito (npm), affecting versions >= 0.0.0. No fixed version is listed yet.
Which versions of passport-cognito are affected by CVE-2019-19723? passport-cognito (npm) versions >= 0.0.0 is affected.
Is there a fix for CVE-2019-19723? No fixed version is listed for CVE-2019-19723 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2019-19723 exploitable, and should I be worried? Whether CVE-2019-19723 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2019-19723 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.