You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-09-19] [$250] Tighten the onyx export masking logic #70107
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: @dylanexpensifyUpwork Automation - Do Not Edit
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
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:
@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]
Activity
melvin-bot commentedon Sep 8, 2025
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.[-]Tighten the onyx export masking logic[/-][+][$250] Tighten the onyx export masking logic[/+]melvin-bot commentedon Sep 8, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021965074993794679004
melvin-bot commentedon Sep 8, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 (
External)4 remaining items
[-][$250] Tighten the onyx export masking logic[/-][+][Due for payment 2025-09-19] [$250] Tighten the onyx export masking logic[/+]melvin-bot commentedon Sep 12, 2025
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:
melvin-bot commentedon Sep 12, 2025
@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]
dylanexpensify commentedon Sep 15, 2025
Payment coming up!
melvin-bot commentedon Sep 19, 2025
Payment Summary
Upwork Job
BugZero Checklist (@dylanexpensify)
dylanexpensify commentedon Sep 23, 2025
Payment summary:
Contributor+: @hungvu193 $250 via NewDot
Please apply/request!
JmillsExpensify commentedon Oct 16, 2025
$250 approved for @hungvu193