Skip to content

omniauth-apple allows attacker to fake their email address during authentication

High severity GitHub Reviewed Published Dec 3, 2020 in nhosoya/omniauth-apple • Updated Nov 6, 2023

Package

bundler omniauth-apple (RubyGems)

Affected versions

< 1.0.1

Patched versions

1.0.1

Description

Impact

This vulnerability impacts applications using the omniauth-apple strategy of OmniAuth and using the info.email field of OmniAuth's Auth Hash Schema for any kind of identification. The value of this field may be set to any value of the attacker's choice including email addresses of other users.

For example, an application using omniauth-apple with the following code will be impacted:

def omniauth_callback
    auth_hash = request.env['omniauth.auth']
    @authenticated_user = User.find_by(email: auth_hash.info.email)
end

Applications not using info.email for identification but are instead using the uid field are not impacted in the same manner. Note, these applications may still be negatively affected if the value of info.email is being used for other purposes.

Patches

Applications using affected versions of omniauth-apple are advised to upgrade to omniauth-apple version 1.0.1 or later.

Workarounds

If unable to upgrade to a patched version, monkey patching OmniAuth::Strategies::Apple#email as follows is advised as a workaround:

module OmniAuth
  module Strategies
    class Apple
      def email
        id_info['email']
      end
    end
  end
end

References

@nhosoya nhosoya published to nhosoya/omniauth-apple Dec 3, 2020
Reviewed Dec 8, 2020
Published to the GitHub Advisory Database Dec 8, 2020
Published by the National Vulnerability Database Dec 8, 2020
Last updated Nov 6, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N

EPSS score

0.131%
(50th percentile)

Weaknesses

CVE ID

CVE-2020-26254

GHSA ID

GHSA-49r3-2549-3633

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.