🔒 replace predictable temp dir with fs.mkdtemp in zip-entries

[sunnylqm]

🎯 What: The enumZipEntries function in src/utils/zip-entries.ts previously used a predictable mechanism based on Date.now() combined with a static prefix to create temporary directories for extracting .hap contents. This vulnerability has been fixed.

⚠️ Risk: The previous approach, which essentially relied on generating predictable identifiers (timestamps), created a predictable temporary file path. This posed a security risk as a malicious process running on the same machine could guess the directory name, potentially leading to unauthorized data access, file tampering, or collision-based Denial of Service before or during extraction.

🛡️ Solution: To mitigate this vulnerability, the fix leverages the secure fs.mkdtemp() method (from the fs-extra/fs.promises library) which appends securely generated pseudo-random characters to the directory prefix. This guarantees directory name uniqueness and prevents prediction by malicious actors. Testing confirmed no regressions in functionality, formatting or performance with zip entry resolution.

---

PR created automatically by Jules for task 16770242411467217764 started by @sunnylqm

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Rate limit exceeded

@sunnylqm has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 49 minutes and 16 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: dbf0927e-e945-471c-a642-165f6ff57f03

📥 Commits

Reviewing files that changed from the base of the PR and between 2be3698 and cfa5dd4.

📒 Files selected for processing (1)

• src/utils/zip-entries.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jules-16770242411467217764-c9bf7970

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}