hj01857655 / kiro-account-manager

1. high Semgrep The application builds a file path from potentially untrusted data, which can lead to a path traversal vulnerability. An attacker can manipulate the path which the application uses to access files. If the application does not validate user input and sanitize file paths, sensitive files such as configuration or user data can be accessed, potentially creating or overwriting files. To prevent this vulnerability, validate and sanitize any input that is used to create references to file paths. Also, enforce strict file access controls. For example, choose privileges allowing public-facing applications to access only the required files. /src-tauri/src/core/paths.rs:117 100%
2. high Semgrep The application builds a file path from potentially untrusted data, which can lead to a path traversal vulnerability. An attacker can manipulate the path which the application uses to access files. If the application does not validate user input and sanitize file paths, sensitive files such as configuration or user data can be accessed, potentially creating or overwriting files. To prevent this vulnerability, validate and sanitize any input that is used to create references to file paths. Also, enforce strict file access controls. For example, choose privileges allowing public-facing applications to access only the required files. /src-tauri/src/services/cli_session_storage.rs:114 100%
3. high Semgrep The application builds a file path from potentially untrusted data, which can lead to a path traversal vulnerability. An attacker can manipulate the path which the application uses to access files. If the application does not validate user input and sanitize file paths, sensitive files such as configuration or user data can be accessed, potentially creating or overwriting files. To prevent this vulnerability, validate and sanitize any input that is used to create references to file paths. Also, enforce strict file access controls. For example, choose privileges allowing public-facing applications to access only the required files. /src-tauri/src/services/cli_session_storage.rs:123 100%
4. high Semgrep The application builds a file path from potentially untrusted data, which can lead to a path traversal vulnerability. An attacker can manipulate the path which the application uses to access files. If the application does not validate user input and sanitize file paths, sensitive files such as configuration or user data can be accessed, potentially creating or overwriting files. To prevent this vulnerability, validate and sanitize any input that is used to create references to file paths. Also, enforce strict file access controls. For example, choose privileges allowing public-facing applications to access only the required files. /src-tauri/src/services/session_storage.rs:174 100%
5. high Semgrep The application builds a file path from potentially untrusted data, which can lead to a path traversal vulnerability. An attacker can manipulate the path which the application uses to access files. If the application does not validate user input and sanitize file paths, sensitive files such as configuration or user data can be accessed, potentially creating or overwriting files. To prevent this vulnerability, validate and sanitize any input that is used to create references to file paths. Also, enforce strict file access controls. For example, choose privileges allowing public-facing applications to access only the required files. /src-tauri/src/services/session_storage.rs:231 100%
6. high Semgrep The application builds a file path from potentially untrusted data, which can lead to a path traversal vulnerability. An attacker can manipulate the path which the application uses to access files. If the application does not validate user input and sanitize file paths, sensitive files such as configuration or user data can be accessed, potentially creating or overwriting files. To prevent this vulnerability, validate and sanitize any input that is used to create references to file paths. Also, enforce strict file access controls. For example, choose privileges allowing public-facing applications to access only the required files. /src-tauri/src/services/session_storage.rs:310 100%
7. high Semgrep Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Be sure to use double-quotes the environment variable, like this: "$ENVVAR". /.github/workflows/build.yml:57 57%
8. high Semgrep Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Be sure to use double-quotes the environment variable, like this: "$ENVVAR". /.github/workflows/release.yml:155 57%
9. high Semgrep Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Be sure to use double-quotes the environment variable, like this: "$ENVVAR". /.github/workflows/release.yml:217 57%
10. high Semgrep Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Be sure to use double-quotes the environment variable, like this: "$ENVVAR". /.github/workflows/release.yml:247 57%
11. high Semgrep Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Be sure to use double-quotes the environment variable, like this: "$ENVVAR". /.github/workflows/release.yml:262 57%
12. high Semgrep Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Be sure to use double-quotes the environment variable, like this: "$ENVVAR". /.github/workflows/release.yml:290 57%
13. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/release.yml:35 52%
14. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/release.yml:195 52%
15. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/release.yml:80 52%
16. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/release.yml:69 52%
17. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/release.yml:64 52%
18. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build.yml:77 52%
19. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build.yml:105 52%
20. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build.yml:111 52%
21. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build.yml:117 52%
22. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build.yml:126 52%
23. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build.yml:166 52%
24. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build.yml:182 52%
25. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/cleanup-runs.yml:18 52%
26. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/release.yml:59 52%
27. low Semgrep Detected string concatenation with a non-literal variable in a util.format / console.log function. If an attacker injects a format specifier in the string, it will forge the log message. Try to use constant values for the format string. /src/utils/errorLogger.ts:11 33%
28. low Dependency checker Loose version constraint: '@radix-ui/react-accordion^1.2.12' — attacker could push malicious update package.json 2%
29. low Dependency checker Loose version constraint: 'vite^5.0.8' — attacker could push malicious update package.json 2%
30. low Dependency checker Loose version constraint: 'typescript^5.9.3' — attacker could push malicious update package.json 2%
31. low Dependency checker Loose version constraint: 'tailwindcss^4.0.0' — attacker could push malicious update package.json 2%
32. low Dependency checker Loose version constraint: '@vitejs/plugin-react^4.2.1' — attacker could push malicious update package.json 2%
33. low Dependency checker Loose version constraint: '@types/react^18.3.18' — attacker could push malicious update package.json 2%
34. low Dependency checker Loose version constraint: '@base-ui/react^1.4.1' — attacker could push malicious update package.json 2%
35. low Dependency checker Loose version constraint: '@radix-ui/react-checkbox^1.3.3' — attacker could push malicious update package.json 2%
36. low Dependency checker Loose version constraint: '@radix-ui/react-dialog^1.1.15' — attacker could push malicious update package.json 2%
37. low Dependency checker Loose version constraint: '@radix-ui/react-dropdown-menu^2.1.16' — attacker could push malicious update package.json 2%
38. low Dependency checker Loose version constraint: '@radix-ui/react-label^2.1.8' — attacker could push malicious update package.json 2%
39. low Dependency checker Loose version constraint: '@radix-ui/react-popover^1.1.15' — attacker could push malicious update package.json 2%
40. low Dependency checker Loose version constraint: '@radix-ui/react-progress^1.1.8' — attacker could push malicious update package.json 2%
41. low Dependency checker Loose version constraint: '@radix-ui/react-scroll-area^1.2.10' — attacker could push malicious update package.json 2%
42. low Dependency checker Loose version constraint: '@radix-ui/react-select^2.2.6' — attacker could push malicious update package.json 2%
43. low Dependency checker Loose version constraint: '@radix-ui/react-separator^1.1.8' — attacker could push malicious update package.json 2%
44. low Dependency checker Loose version constraint: '@radix-ui/react-slot^1.2.4' — attacker could push malicious update package.json 2%
45. low Dependency checker Loose version constraint: '@radix-ui/react-switch^1.2.6' — attacker could push malicious update package.json 2%
46. low Dependency checker Loose version constraint: '@radix-ui/react-tabs^1.1.13' — attacker could push malicious update package.json 2%
47. low Dependency checker Loose version constraint: '@radix-ui/react-tooltip^1.2.8' — attacker could push malicious update package.json 2%
48. low Dependency checker Loose version constraint: '@tauri-apps/plugin-fs^2.4.5' — attacker could push malicious update package.json 2%
49. low Dependency checker Loose version constraint: '@tauri-apps/plugin-process^2.3.1' — attacker could push malicious update package.json 2%
50. low Dependency checker Loose version constraint: '@types/react-dom^18.3.5' — attacker could push malicious update package.json 2%
51. low Dependency checker Loose version constraint: '@types/node^25.6.0' — attacker could push malicious update package.json 2%
52. low Dependency checker Loose version constraint: '@tailwindcss/vite^4.0.0' — attacker could push malicious update package.json 2%
53. low Dependency checker Loose version constraint: 'tw-animate-css^1.4.0' — attacker could push malicious update package.json 2%
54. low Dependency checker Loose version constraint: 'tailwind-merge^3.4.0' — attacker could push malicious update package.json 2%
55. low Dependency checker Loose version constraint: 'sonner^2.0.7' — attacker could push malicious update package.json 2%
56. low Dependency checker Loose version constraint: 'recharts^3.10.1' — attacker could push malicious update package.json 2%
57. low Dependency checker Loose version constraint: 'react-dom^18.2.0' — attacker could push malicious update package.json 2%
58. low Dependency checker Loose version constraint: 'react^18.2.0' — attacker could push malicious update package.json 2%
59. low Dependency checker Loose version constraint: 'next-themes^0.4.6' — attacker could push malicious update package.json 2%
60. low Dependency checker Loose version constraint: 'lucide-react^0.294.0' — attacker could push malicious update package.json 2%
61. low Dependency checker Loose version constraint: 'cmdk^1.1.1' — attacker could push malicious update package.json 2%
62. low Dependency checker Loose version constraint: 'clsx^2.1.1' — attacker could push malicious update package.json 2%
63. low Dependency checker Loose version constraint: 'class-variance-authority^0.7.1' — attacker could push malicious update package.json 2%
64. low Dependency checker Loose version constraint: '@tauri-apps/plugin-opener^2.5.3' — attacker could push malicious update package.json 2%
65. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /.github/workflows/release.yml 0%
66. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /.github/workflows/build.yml 0%

No findings match these filters. Clear filters