CyberSecurity SEE

Microsoft Edge Discovered Storing Saved Credentials in Plaintext Memory

Microsoft Edge Discovered Storing Saved Credentials in Plaintext Memory

Security Flaw in Microsoft Edge Exposes User Passwords: A Closer Look

Security researcher Tom Jøran Sønstebyseter Rønning, known online by his handle @L1v1ng0ffTh3L4N, has made a alarming revelation regarding the Microsoft Edge browser. His findings indicate that upon startup, Edge decrypts every saved password, storing them in cleartext within the process memory for the duration of the user’s session. This means that not only are passwords for currently visited websites accessible, but also every credential a user ever saved is exposed in a readable format as soon as Edge is launched.

This serious vulnerability raises considerable concerns regarding user security and privacy. The decrypted passwords remain in memory from the moment the browser opens, making them potentially accessible to malicious actors or poorly designed software.

The Underlying Assumptions and Risks

Uzair Gadit, the Founder and CEO of Secure.com, has weighed in on these troubling findings, noting that it isn’t just the technical behavior of Edge that is alarming; it is the implicit assumptions users make about password security. Many users adhere to best practices by utilizing strong passwords and relying on password managers. However, the issue arises with the design choices made by the software itself—choices that may expose those very credentials without user knowledge.

Gadit explains that while requiring administrative access may seem like a safeguard, it is ironically where numerous enterprise breaches initiate. "Once an attacker gains privileged access in shared environments like RDS or Citrix, the difference between decrypting credentials on demand versus having them all present in memory is vast," he stated. This change in status could transform a single compromised account into an extensive credential exposure incident impacting multiple users.

He argues that the cybersecurity sector must recalibrate its focus. The conversation should shift away from merely improving password hygiene and highlight the greater issue of exposure. “The real concern is not just the strength of the password,” he notes, “but how long it remains usable, where it exists, and who has access to it.”

The Dangers of Decrypted State

Gadit emphasizes the importance of minimizing the time credentials exist in plaintext to mitigate risk. The architectural design choice to keep everything decrypted for convenience only heightens vulnerabilities. In an era where attackers increasingly employ automation and artificial intelligence, retaining decrypted passwords can significantly amplify risk levels.

“World Password Day often redirects attention toward user behavior,” Gadit remarked. “However, this serves as a reminder that the greater risk frequently lies one layer below that—within the design decisions made by those who create trusted tools. If usability is prioritized over reducing exposure, even impeccable password hygiene will not guarantee the security outcomes that organizations expect.”

His position underscores that the challenge is not solely with weak passwords, but with the broader issue of credential exposure being overlooked in system design. Gadit warns that until this perspective alters, attackers will concentrate less on penetrating systems and more on exploiting accessible information once they gain entry.

A Wider Trust Boundary Challenge

Ted Miracco, the CEO of Approov, has also commented on the ramifications of this exposure. He highlights that incidents like these emphasize a more extensive trust boundary issue. Modern infostealers thrive on the chasm between being “encrypted at rest” and being “exposed at runtime.” Miracco advocates for a shift within the industry towards app-bound, just-in-time access to sensitive information rather than maintaining long-lived plaintext copies in memory.

He points out that even when credentials are stored securely, handling them in cleartext makes them vulnerable to any process capable of observing memory or intercepting execution flows. "Without enforcing robust runtime protections and restricting the methods by which credentials can be accessed or reused, attackers can evade traditional security measures without ever needing to break encryption,” he cautioned.

Conclusion

The implications of Rønning’s findings regarding Microsoft Edge extend beyond mere technical anomalies; they point toward a systemic flaw in how security is approached within widely used software. As discussions concerning cybersecurity evolve, it becomes increasingly critical to consider not only the performance and convenience of tools but also how their inherent design decisions impact user security. As users remain vigilant about individual password hygiene, organizations must also ensure that their software prioritizes robust security mechanisms to mitigate risks associated with credential exposure.

Source link

Exit mobile version