Skip to content

Add destination path validation for certificate deployment#2658

Open
lucygramley wants to merge 2 commits into
microsoft:masterfrom
lucygramley:fix/cert-destination-path-validation
Open

Add destination path validation for certificate deployment#2658
lucygramley wants to merge 2 commits into
microsoft:masterfrom
lucygramley:fix/cert-destination-path-validation

Conversation

@lucygramley
Copy link
Copy Markdown
Contributor

  • Validate destination paths against allowed platform-specific directories before writing certificate files.
  • Await CSR app name extraction before performing filesystem operations.
  • Reject paths containing traversal sequences.

- Validate destination path against allowed platform-specific directories before writing certificate files
- Await CSR app name validation before performing any filesystem operations
- Reject paths containing traversal sequences

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@joj joj enabled auto-merge May 27, 2026 23:09
@ConnorQi01
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@ConnorQi01
Copy link
Copy Markdown
Collaborator

Thanks for the contribution and for working on certificate deployment path validation.

Could you please create or link a corresponding issue for this PR? It would help us track the affected certificate deployment flow, the expected mitigation, and the platform-specific assumptions.

The unit test pipeline is currently failing on Linux, Windows, and macOS. Could you please inspect the failing logs and update the PR?

For this change, I would especially suggest adding or updating tests around the allowed destination paths for iOS, macOS, and Windows. The new allowlist looks fairly strict, so we should verify that valid simulator/device certificate deployment paths still work while traversal or unexpected paths are rejected.

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.

3 participants