Skip to content

Conversation

@Gering112
Copy link
Contributor

No description provided.

@Gering112 Gering112 merged commit 80ee84c into DEV-115700 Oct 14, 2025
1 of 2 checks passed
@Gering112 Gering112 deleted the DEV-116726 branch October 14, 2025 16:10
@zeropath-ai
Copy link

zeropath-ai bot commented Oct 14, 2025

The following issues were found:

The following low severity issues were also found:

  • Business Logic Problem: No patch for this bug could be generated. Here is a description and location:
    Location: riskified-sdk/src/main/java/com/riskified/models/BankWirePaymentDetails.java:38:52
    Description: Syntax / logical errors introduced: methods use undefined identifier 'self' instead of 'this', setters assign Date values to the String field 'token', and method names contain typos (getStoredPaymentUpdateddAt). These are present in BankWirePaymentDetails and will cause compile errors or incorrect behavior (data corruption). In particular, setStoredPaymentCreatedAt and setStoredPaymentUpdateddAt assign a Date to this.token (String) which is a type/logic error; using 'self' will fail to compile in Java. These problems can break builds or cause incorrect handling of sensitive payment token data.
    Link to UI: https://zeropath.com/app/issues/441dc5a9-2c37-46b1-a3fe-bf7ce142fd5b
  • Business Logic Problem: No patch for this bug could be generated. Here is a description and location:
    Location: riskified-sdk/src/main/java/com/riskified/models/BankWirePaymentDetails.java:42:52
    Description: Potential sensitive-data corruption / logic bug: the setters setStoredPaymentCreatedAt and setStoredPaymentUpdateddAt assign to the 'token' field (a String) instead of the corresponding Date fields. This incorrectly mutates/overwrites the payment token and is likely to break authentication/authorization flows that rely on token integrity.
    Link to UI: https://zeropath.com/app/issues/07864bfc-3785-49e7-916c-11dbad9d7dd8

Reply to this PR with @zeropath-ai followed by a description of what change you want and we'll auto-submit a change to this PR to implement it.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants