Skip to content

Issuance request forwarding: Documenting the threat - #550

Draft
simoneonofri wants to merge 1 commit into
mainfrom
issue-382-wallet-selection-threat
Draft

Issuance request forwarding: Documenting the threat#550
simoneonofri wants to merge 1 commit into
mainfrom
issue-382-wallet-selection-threat

Conversation

@simoneonofri

@simoneonofri simoneonofri commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

This PR adds the issuance request forwarding threat to the Security Considerations threat model.

The threat captures the case discussed in #382 where a malicious holder's credential manager, such as a digital wallet, is selected by the user during issuance and forwards the issuance request data to another credential manager on an attacker-controlled device.

Addressing this threat remains under discussion in #382.

Related to #382.


Preview | Diff

@simoneonofri simoneonofri added security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response. security-considerations labels Jul 8, 2026
Comment thread index.html
Comment on lines +1873 to +1874
causing issuance to complete with that other credential manager
rather than with the credential manager selected by the user.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably add a note that authorization steps in the protocol might mitigate this? So the result doesn't have to be the issuance to complete.

Something like this?

Suggested change
causing issuance to complete with that other credential manager
rather than with the credential manager selected by the user.
causing issuance to complete with that other credential manager
rather than with the credential manager selected by the user. Note
that the success of such an attack also depends on possible
authorization steps performed by the underlying
[=digital credential/issuance protocols=].

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "the success of such an attack" reads a little weird.

Projecting forward to the actual mitigation text, what mitigations are in place, for instance, in Openid4vci?

With an example of a mitigation, we might be able to reframe the note a bit.

Comment thread index.html
<strong>Issuance Request Forwarding</strong>
</dt>
<dd>
A malicious [=holder's=] [=credential manager=], such as a digital

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it the holder that is malicious, or is it the credential manager? A little rephrasing should be done to make this clear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

security-considerations security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants