drupal / drupal

1. high Semgrep The 'phpinfo' function may reveal sensitive information about your environment. /core/modules/system/src/Controller/SystemInfoController.php:83 50%
2. high Semgrep Executing non-constant commands. This can lead to command injection. /composer/Composer.php:86 43%
3. high Semgrep Executing non-constant commands. This can lead to command injection. /core/lib/Drupal/Core/Command/ServerCommand.php:237 43%
4. high YARA YARA rule matched: detect_base64_exec — Encoded payload decoded and then executed /core/assets/vendor/ckeditor5/ckeditor5.umd.js 3%
5. high YARA YARA rule matched: detect_base64_exec — Encoded payload decoded and then executed /core/assets/vendor/ckeditor5/ckeditor5.umd.js.map 3%
6. high YARA YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together /core/assets/vendor/ckeditor5/ckeditor5.umd.js.map 1%
7. high YARA YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together /core/assets/vendor/jquery/jquery.min.js 1%
8. high YARA YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together /core/assets/vendor/transliteration/bundle.umd.min.js.map 1%
9. high YARA YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together /core/assets/vendor/transliteration/bundle.umd.min.js 1%
10. high YARA YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together /core/assets/vendor/jquery/jquery.js 1%
11. high YARA YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together /core/assets/vendor/ckeditor5/ckeditor5.umd.js 1%
12. medium Semgrep RegExp() called with a `config` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-controlled input, consider performing input validation or use a regex checking/sanitization library such as https://www.npmjs.com/package/recheck to verify that the regex does not appear vulnerable to ReDoS. /core/modules/ckeditor5/js/ckeditor5.js:89 100%
13. medium Semgrep RegExp() called with a `event` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-controlled input, consider performing input validation or use a regex checking/sanitization library such as https://www.npmjs.com/package/recheck to verify that the regex does not appear vulnerable to ReDoS. /core/modules/file/js/file.js:161 100%
14. medium Semgrep RegExp() called with a `response` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-controlled input, consider performing input validation or use a regex checking/sanitization library such as https://www.npmjs.com/package/recheck to verify that the regex does not appear vulnerable to ReDoS. /core/modules/views_ui/js/ajax.js:142 100%
15. medium Semgrep RegExp() called with a `settings` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-controlled input, consider performing input validation or use a regex checking/sanitization library such as https://www.npmjs.com/package/recheck to verify that the regex does not appear vulnerable to ReDoS. /core/misc/machine-name.js:45 100%
16. medium Semgrep This code contains bidirectional (bidi) characters. While this is useful for support of right-to-left languages such as Arabic or Hebrew, it can also be used to trick language parsers into executing code in a manner that is different from how it is displayed in code editing and review tools. If this is not what you were expecting, please review this code in an editor that can reveal hidden Unicode characters. /core/lib/Drupal/Core/Language/LanguageManager.php:276 100%
17. medium Semgrep This code contains bidirectional (bidi) characters. While this is useful for support of right-to-left languages such as Arabic or Hebrew, it can also be used to trick language parsers into executing code in a manner that is different from how it is displayed in code editing and review tools. If this is not what you were expecting, please review this code in an editor that can reveal hidden Unicode characters. /core/lib/Drupal/Core/Language/LanguageManager.php:314 100%
18. medium Semgrep This code contains bidirectional (bidi) characters. While this is useful for support of right-to-left languages such as Arabic or Hebrew, it can also be used to trick language parsers into executing code in a manner that is different from how it is displayed in code editing and review tools. If this is not what you were expecting, please review this code in an editor that can reveal hidden Unicode characters. /core/lib/Drupal/Core/Language/LanguageManager.php:315 100%
19. medium Semgrep This code contains bidirectional (bidi) characters. While this is useful for support of right-to-left languages such as Arabic or Hebrew, it can also be used to trick language parsers into executing code in a manner that is different from how it is displayed in code editing and review tools. If this is not what you were expecting, please review this code in an editor that can reveal hidden Unicode characters. /core/lib/Drupal/Core/Language/LanguageManager.php:339 100%
20. medium Semgrep This code contains bidirectional (bidi) characters. While this is useful for support of right-to-left languages such as Arabic or Hebrew, it can also be used to trick language parsers into executing code in a manner that is different from how it is displayed in code editing and review tools. If this is not what you were expecting, please review this code in an editor that can reveal hidden Unicode characters. /core/lib/Drupal/Core/Language/LanguageManager.php:341 100%
21. medium Semgrep This code contains bidirectional (bidi) characters. While this is useful for support of right-to-left languages such as Arabic or Hebrew, it can also be used to trick language parsers into executing code in a manner that is different from how it is displayed in code editing and review tools. If this is not what you were expecting, please review this code in an editor that can reveal hidden Unicode characters. /core/lib/Drupal/Core/Language/LanguageManager.php:363 100%
22. medium Semgrep This code contains bidirectional (bidi) characters. While this is useful for support of right-to-left languages such as Arabic or Hebrew, it can also be used to trick language parsers into executing code in a manner that is different from how it is displayed in code editing and review tools. If this is not what you were expecting, please review this code in an editor that can reveal hidden Unicode characters. /core/lib/Drupal/Core/Language/LanguageManager.php:264 100%
23. medium Semgrep This code contains bidirectional (bidi) characters. While this is useful for support of right-to-left languages such as Arabic or Hebrew, it can also be used to trick language parsers into executing code in a manner that is different from how it is displayed in code editing and review tools. If this is not what you were expecting, please review this code in an editor that can reveal hidden Unicode characters. /core/lib/Drupal/Core/Language/LanguageManager.php:241 100%
24. medium Semgrep It looks like MD5 is used as a password hash. MD5 is not considered a secure password hash because it can be cracked by an attacker in a short amount of time. Use a suitable password hashing function such as bcrypt. You can use `password_hash($PASSWORD, PASSWORD_BCRYPT, $OPTIONS);`. /core/lib/Drupal/Core/Password/PhpassHashedPasswordBase.php:224 99%
25. medium GuardDog Detects unicode homoglyphs and uncommon characters used for obfuscation [threat-runtime-obfuscation-unicode] /core/assets/vendor/ckeditor5/translations/bg.umd.js:7 98%
26. medium Semgrep This .yarnrc.yml does not set a minimal age gate or sets it too low. Newly published packages can be malicious or unstable. Add `npmMinimalAgeGate: "7d"` to wait 7 days before resolving newly published package versions. Added in: 4.10 Reference: https://yarnpkg.com/configuration/yarnrc#npmMinimalAgeGate /core/.yarnrc.yml:8 96%
27. medium Semgrep File name based on user input risks server-side request forgery. /.gitlab-ci/scripts/component-coverage-metrics.php:45 55%
28. medium Semgrep File name based on user input risks server-side request forgery. /.gitlab-ci/scripts/phpstan-baseline-statistics.php:43 55%
29. medium Semgrep File name based on user input risks server-side request forgery. /.gitlab-ci/scripts/phpstan-baseline-statistics.php:54 55%
30. medium Semgrep File name based on user input risks server-side request forgery. /core/assets/scaffold/files/ht.router.php:34 55%
31. medium Semgrep File name based on user input risks server-side request forgery. /.gitlab-ci/scripts/component-coverage-metrics.php:27 55%
32. medium Semgrep File name based on user input risks server-side request forgery. /.gitlab-ci/scripts/component-coverage-metrics.php:37 55%
33. medium Semgrep File name based on user input risks server-side request forgery. /.ht.router.php:34 55%
34. medium Semgrep File name based on user input risks server-side request forgery. /.ht.router.php:47 55%
35. medium Semgrep File name based on user input risks server-side request forgery. /core/assets/scaffold/files/ht.router.php:47 55%
36. medium Semgrep Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues /core/lib/Drupal/Component/Transliteration/PhpTransliteration.php:158 54%
37. medium Semgrep The `redirect()` method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an allowlist to validate URLs. /core/modules/user/src/Controller/UserController.php:485 49%
38. medium Semgrep The `redirect()` method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an allowlist to validate URLs. /core/modules/user/src/Controller/UserController.php:400 49%
39. medium Semgrep The `redirect()` method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an allowlist to validate URLs. /core/modules/user/src/Controller/UserController.php:375 49%
40. medium Semgrep The `redirect()` method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an allowlist to validate URLs. /core/modules/user/src/Controller/UserController.php:301 49%
41. medium Semgrep The `redirect()` method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an allowlist to validate URLs. /core/modules/user/src/Controller/UserController.php:143 49%
42. medium Semgrep The `redirect()` method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an allowlist to validate URLs. /core/modules/comment/src/Controller/CommentController.php:179 49%
43. medium Semgrep The `redirect()` method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an allowlist to validate URLs. /core/lib/Drupal/Core/Entity/Controller/EntityController.php:149 49%
44. medium Semgrep The `redirect()` method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an allowlist to validate URLs. /core/modules/node/src/Controller/NodeController.php:96 49%
45. medium Semgrep The `redirect()` method does not check its destination in any way. If you redirect to a URL provided by end-users, your application may be open to the unvalidated redirects security vulnerability. Consider using literal values or an allowlist to validate URLs. /core/modules/user/src/Controller/UserController.php:182 49%
46. medium Semgrep Detection of insertAdjacentHTML from non-constant definition. This can inadvertently expose users to cross-site scripting (XSS) attacks if this comes from user-provided input. If you have to use insertAdjacentHTML, consider using a sanitization library such as DOMPurify to sanitize your HTML. /core/modules/navigation/js/tooltip.js:51 48%
47. medium Semgrep Possibility of prototype polluting function detected. By adding or modifying attributes of an object prototype, it is possible to create attributes that exist on every object, or replace critical attributes with malicious ones. This can be problematic if the software depends on existence or non-existence of certain attributes, or uses pre-defined attributes of object prototype (such as hasOwnProperty, toString or valueOf). Possible mitigations might be: freezing the object prototype, using an object without prototypes (via Object.create(null) ), blocking modifications of attributes that resolve to object prototype, using Map instead of object. /core/misc/tableselect.js:154 44%
48. medium Semgrep RegExp() called with a `e` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-controlled input, consider performing input validation or use a regex checking/sanitization library such as https://www.npmjs.com/package/recheck to verify that the regex does not appear vulnerable to ReDoS. /core/modules/system/js/system.modules.js:40 40%
49. medium Semgrep RegExp() called with a `e` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-controlled input, consider performing input validation or use a regex checking/sanitization library such as https://www.npmjs.com/package/recheck to verify that the regex does not appear vulnerable to ReDoS. /core/modules/user/js/user.permissions.js:155 40%
50. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/migrate/src/Plugin/migrate/source/ConfigEntity.php:75 36%
51. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/user/src/UserData.php:62 36%
52. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Component/Plugin/Discovery/AttributeClassDiscovery.php:91 36%
53. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/migrate/migrate.api.php:159 36%
54. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/migrate/migrate.api.php:182 36%
55. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/migrate/src/Plugin/Discovery/AnnotatedClassDiscoveryAutomatedProviders.php:69 36%
56. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/user/src/UserData.php:47 36%
57. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/user/src/UserData.php:55 36%
58. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/user/src/UserData.php:68 36%
59. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php:2127 36%
60. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/views/src/Plugin/views/field/Serialized.php:76 36%
61. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/views/src/Plugin/views/field/Serialized.php:73 36%
62. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/serialization/src/Normalizer/PrimitiveDataNormalizer.php:40 36%
63. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/layout_builder/src/Plugin/Block/InlineBlock.php:262 36%
64. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/layout_builder/src/Plugin/Block/InlineBlock.php:218 36%
65. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/dblog/src/Plugin/views/field/DblogMessage.php:62 36%
66. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/modules/dblog/src/Controller/DbLogController.php:358 36%
67. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/Validation/Plugin/Validation/Constraint/SerializedConstraintValidator.php:33 36%
68. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/Routing/RouteProvider.php:332 36%
69. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/Queue/DatabaseQueue.php:150 36%
70. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/Cache/MemoryBackend.php:99 36%
71. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/Config/DatabaseStorage.php:275 36%
72. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/Batch/BatchStorage.php:67 36%
73. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Component/Serialization/PhpSerialize.php:21 36%
74. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Component/Plugin/Discovery/AttributeClassDiscovery.php:93 36%
75. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Component/DependencyInjection/Container.php:166 36%
76. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/Routing/RouteProvider.php:303 36%
77. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Component/Annotation/Plugin/Discovery/AnnotatedClassDiscovery.php:128 36%
78. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/DefaultContent/Exporter.php:260 36%
79. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/Field/Plugin/Field/FieldType/MapItem.php:69 36%
80. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/Menu/MenuTreeParameters.php:222 36%
81. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/Menu/MenuTreeStorage.php:658 36%
82. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/Menu/MenuTreeStorage.php:777 36%
83. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/Queue/Batch.php:31 36%
84. medium Semgrep Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers). /core/lib/Drupal/Core/Queue/Batch.php:61 36%
85. medium Semgrep Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. /core/lib/Drupal/Component/PhpStorage/MTimeProtectedFastFileStorage.php:173 21%
86. medium Semgrep Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. /core/modules/sqlite/src/Driver/Database/sqlite/Connection.php:182 21%
87. medium Semgrep Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. /core/lib/Drupal/Core/File/FileSystem.php:105 20%
88. medium Semgrep Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. /core/modules/package_manager/src/FailureMarker.php:47 20%
89. medium Semgrep Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. /core/lib/Drupal/Core/File/FileSystem.php:404 20%
90. medium Semgrep Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. /core/lib/Drupal/Core/File/FileSystem.php:108 20%
91. medium Semgrep Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. /core/lib/Drupal/Component/PhpStorage/FileStorage.php:184 20%
92. low Semgrep Translated strings will not be escaped when rendered in a template. This leads to a vulnerability where translators could include malicious script tags in their translations. Consider using `force_escape` to explicitly escape a translated text. /core/modules/workflows/help_topics/workflows.overview.html.twig:10 98%
93. low GuardDog Detects heavy obfuscation techniques commonly used by malware [threat-runtime-obfuscation] /core/assets/vendor/transliteration/bundle.umd.min.js:1 95%
94. 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 /core/INSTALL.txt 0%

No findings match these filters. Clear filters