Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OID4VCI: distinguish two types of pre-auth code abuse. #23

Open
OIDF-automation opened this issue Feb 28, 2023 · 0 comments · May be fixed by #464
Open

OID4VCI: distinguish two types of pre-auth code abuse. #23

OIDF-automation opened this issue Feb 28, 2023 · 0 comments · May be fixed by #464

Comments

@OIDF-automation
Copy link
Contributor

OIDF-automation commented Feb 28, 2023

Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/1838

Original Reporter: KristinaYasuda

TODO The spec does not distinguish between replay (attacker forwards code to other wallet/end-user) and stealing the code (attacker scans code intended for other user). This needs to be fixed.

From the security analysis: openid / connect / Pull Request #468: First draft of OpenID 4 VC Security Analysis — Bitbucket cc @danielfett

@Sakurann Sakurann added security and removed bug labels Sep 30, 2023
@Sakurann Sakurann added this to the Final 1.0 milestone Dec 18, 2024
surfnet-niels pushed a commit to surfnet-niels/OpenID4VCI that referenced this issue Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants