Researchers find bug allowing hackers to bypass first factor authentication of users accounts

Found by Duo security in a third-party library in its own authentication gateway

Researchers uncovered a bug that could have allowed cyber crooks to bypass the first authentication step of user accounts protected by single sign-on (SSO).

Found by security company Duo, the firm discovered the implementation flaw in a third-party library in its own authentication gateway, Duo Network Gateway (DNG), late last year. After giving vendors time to fix the bug, it disclosed the problem responsibly. It's only now that the details of how worryingly effective the bug is have gone public.

Located in the open-source library 'python-saml' (CVE-2017-11427), the firm's researchers said that under certain configurations, the flaw could have allowed an attacker with authenticated access to a SAML Identity Provider (IdP) to bypass the first factor of authentication for a different user.

After a bit of digging, it was revealed that the flaw was reflected in many other SSO applications, thanks to a problem in handling the underlying "authentication language", something which has become a standard for products in this space.

"This issue is due to an inconsistency of XML DOM traversal APIs and their handling of comment nodes," Duo explained in a blog post. "Comment nodes should have no effect - and indeed, due to the canonicalisation of XML prior to signature verification, inserting an XML comment into a SAML message does not invalidate its signature."

However, the firm said the 'python-saml' code makes incorrect use of a DOM-traversal API, such that it fails to extract the full inner text of an XML element containing a comment. Instead, all the text after the comment is lost.

"To exploit this issue, an attacker inserts XML comments into select areas of the SAML assertions before passing them along to the DNG," the firm continued. "Once the DNG validates the signature and extracts the user's identifier, only part of the user's identifier is recovered."

Duo said that in cases where an attacker's user identifier (for example: john_doe) can be truncated to become a victim's user identifier (for example: john), the attacker can trick the DNG into authenticating as the victim.

Luckily, however, the issue has been resolved now through a patch to the Duo Network Gateway, and its public announcement has allowed other security firms to fix potentially similar issues in their authentication gateways.

Main image credit: Shutterstock 

Featured Resources

Consumer choice and the payment experience

A software provider's guide to getting, growing, and keeping customers

Download now

Prevent fraud and phishing attacks with DMARC

How to use domain-based message authentication, reporting, and conformance for email security

Download now

Business in the new economy landscape

How we coped with 2020 and looking ahead to a brighter 2021

Download now

How to increase cyber resilience within your organisation

Cyber resilience for dummies

Download now

Recommended

Splunk debuts a new suite of cloud security solutions
Security

Splunk debuts a new suite of cloud security solutions

22 Jun 2021
Nvidia Jetson chips make IoT devices vulnerable to attack
vulnerability

Nvidia Jetson chips make IoT devices vulnerable to attack

22 Jun 2021
Cryptocurrency crimes have increased 12-fold since 2016
cryptocurrencies

Cryptocurrency crimes have increased 12-fold since 2016

22 Jun 2021
University Medical Center Mainz taps IBM to secure health care data
cloud security

University Medical Center Mainz taps IBM to secure health care data

21 Jun 2021

Most Popular

How to find RAM speed, size and type
Laptops

How to find RAM speed, size and type

16 Jun 2021
Q&A: Enabling transformation
Sponsored

Q&A: Enabling transformation

10 Jun 2021
What is HTTP error 400 and how do you fix it?
Network & Internet

What is HTTP error 400 and how do you fix it?

16 Jun 2021