Skip to content

[Due for payment 2025-09-19] [$250] Tighten the onyx export masking logic #70107

Closed

Description

@mountiny

From here

Background

Currently some fields are left behind in state masking which is a security vulnerability. We need to make sure that no private information is shared when exporting one's Onyx state through Troubleshoot.

Problem

When users export their Onyx state through the Troubleshoot feature, sensitive personal data remains visible in the exported text files, which creates a security vulnerability that could lead to unauthorized account access.

Solution

Expand the masking rules so that no private information is shared when exporting one’s Onyx state through Troubleshoot.
You can find the list of keys in attached file. This is not sensitive information per se, but its not needed for the purpose of exporting the onyx state so we can mask it

Issue OwnerCurrent Issue Owner: @dylanexpensify
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021965074993794679004
  • Upwork Job ID: 1965074993794679004
  • Last Price Increase: 2025-09-08

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 8, 2025
  2. melvin-bot commented on Sep 8, 2025

    @melvin-bot

    Triggered auto assignment to @dylanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Sep 8, 2025
  4. changed the title [-]Tighten the onyx export masking logic[/-] [+][$250] Tighten the onyx export masking logic[/+] on Sep 8, 2025
  5. melvin-bot commented on Sep 8, 2025

    @melvin-bot
  6. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Sep 8, 2025
  7. melvin-bot commented on Sep 8, 2025

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 (External)

  8. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Sep 8, 2025
  9. 4 remaining items

  10. changed the title [-][$250] Tighten the onyx export masking logic[/-] [+][Due for payment 2025-09-19] [$250] Tighten the onyx export masking logic[/+] on Sep 12, 2025
  11. melvin-bot commented on Sep 12, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.12-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-09-19. 🎊

    For reference, here are some details about the assignees on this issue:

    • @hungvu193 requires payment through NewDot Manual Requests
    • @MrMuzyk does not require payment (Contractor)
  12. melvin-bot commented on Sep 12, 2025

    @melvin-bot

    @hungvu193 @dylanexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  13. dylanexpensify commented on Sep 15, 2025

    @dylanexpensify
    Contributor

    Payment coming up!

  14. melvin-bot commented on Sep 19, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Reviewer: @hungvu193 owed $250 via NewDot
    • Contributor: @MrMuzyk is from an agency-contributor and not due payment

    BugZero Checklist (@dylanexpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1965074993794679004/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  15. dylanexpensify commented on Sep 23, 2025

    @dylanexpensify
    Contributor

    Payment summary:

    Contributor+: @hungvu193 $250 via NewDot

    Please apply/request!

  16. JmillsExpensify commented on Oct 16, 2025

    @JmillsExpensify
    Contributor

    $250 approved for @hungvu193

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions