janissary 7.3.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- janissary-7.3.0/LICENSE +202 -0
- janissary-7.3.0/PKG-INFO +287 -0
- janissary-7.3.0/README.md +249 -0
- janissary-7.3.0/pyproject.toml +96 -0
- janissary-7.3.0/setup.cfg +4 -0
- janissary-7.3.0/src/janissary/__init__.py +3 -0
- janissary-7.3.0/src/janissary/__main__.py +6 -0
- janissary-7.3.0/src/janissary/agent/__init__.py +25 -0
- janissary-7.3.0/src/janissary/agent/adapters.py +177 -0
- janissary-7.3.0/src/janissary/agent/agent.py +191 -0
- janissary-7.3.0/src/janissary/agent/finding_store.py +225 -0
- janissary-7.3.0/src/janissary/agent/platform_kb.py +195 -0
- janissary-7.3.0/src/janissary/attack/__init__.py +48 -0
- janissary-7.3.0/src/janissary/attack/nuclei.py +279 -0
- janissary-7.3.0/src/janissary/attack/sqli_union.py +494 -0
- janissary-7.3.0/src/janissary/auth.py +134 -0
- janissary-7.3.0/src/janissary/cli.py +1278 -0
- janissary-7.3.0/src/janissary/credentials/__init__.py +0 -0
- janissary-7.3.0/src/janissary/credentials/export.py +62 -0
- janissary-7.3.0/src/janissary/credentials/git_history.py +244 -0
- janissary-7.3.0/src/janissary/credentials/rules.py +381 -0
- janissary-7.3.0/src/janissary/credentials/scanner.py +428 -0
- janissary-7.3.0/src/janissary/detection/__init__.py +38 -0
- janissary-7.3.0/src/janissary/detection/analyzer.py +1116 -0
- janissary-7.3.0/src/janissary/engine/__init__.py +0 -0
- janissary-7.3.0/src/janissary/engine/grouping.py +123 -0
- janissary-7.3.0/src/janissary/engine/scanner.py +865 -0
- janissary-7.3.0/src/janissary/integrations/__init__.py +89 -0
- janissary-7.3.0/src/janissary/integrations/graphql.py +655 -0
- janissary-7.3.0/src/janissary/integrations/websocket.py +248 -0
- janissary-7.3.0/src/janissary/integrations/xmlrpc.py +584 -0
- janissary-7.3.0/src/janissary/legal.py +207 -0
- janissary-7.3.0/src/janissary/output/__init__.py +22 -0
- janissary-7.3.0/src/janissary/output/emitter.py +317 -0
- janissary-7.3.0/src/janissary/output/raw_http.py +86 -0
- janissary-7.3.0/src/janissary/recon/__init__.py +29 -0
- janissary-7.3.0/src/janissary/recon/admin.py +340 -0
- janissary-7.3.0/src/janissary/recon/fingerprint.py +377 -0
- janissary-7.3.0/src/janissary/recon/pacer.py +151 -0
- janissary-7.3.0/src/janissary/recon/waf.py +252 -0
- janissary-7.3.0/src/janissary/reporting/__init__.py +0 -0
- janissary-7.3.0/src/janissary/scope.py +218 -0
- janissary-7.3.0/src/janissary.egg-info/PKG-INFO +287 -0
- janissary-7.3.0/src/janissary.egg-info/SOURCES.txt +46 -0
- janissary-7.3.0/src/janissary.egg-info/dependency_links.txt +1 -0
- janissary-7.3.0/src/janissary.egg-info/entry_points.txt +2 -0
- janissary-7.3.0/src/janissary.egg-info/requires.txt +21 -0
- janissary-7.3.0/src/janissary.egg-info/top_level.txt +1 -0
janissary-7.3.0/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
janissary-7.3.0/PKG-INFO
ADDED
|
@@ -0,0 +1,287 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: janissary
|
|
3
|
+
Version: 7.3.0
|
|
4
|
+
Summary: Differential DAST for teams who need results they can trust.
|
|
5
|
+
Author-email: Hetaireia <hetaireia.it@gmail.com>
|
|
6
|
+
License-Expression: Apache-2.0
|
|
7
|
+
Project-URL: Homepage, https://github.com/Hetaireia/janissary
|
|
8
|
+
Project-URL: Documentation, https://github.com/Hetaireia/janissary/tree/main/docs
|
|
9
|
+
Project-URL: Issues, https://github.com/Hetaireia/janissary/issues
|
|
10
|
+
Keywords: security,dast,pentest,scanner,vulnerability
|
|
11
|
+
Classifier: Development Status :: 4 - Beta
|
|
12
|
+
Classifier: Intended Audience :: Information Technology
|
|
13
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
14
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
15
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
16
|
+
Classifier: Topic :: Security
|
|
17
|
+
Requires-Python: >=3.10
|
|
18
|
+
Description-Content-Type: text/markdown
|
|
19
|
+
License-File: LICENSE
|
|
20
|
+
Requires-Dist: requests>=2.31
|
|
21
|
+
Requires-Dist: websockets>=12.0
|
|
22
|
+
Requires-Dist: defusedxml>=0.7
|
|
23
|
+
Provides-Extra: yaml
|
|
24
|
+
Requires-Dist: pyyaml>=6.0; extra == "yaml"
|
|
25
|
+
Provides-Extra: browser
|
|
26
|
+
Requires-Dist: playwright>=1.40; extra == "browser"
|
|
27
|
+
Provides-Extra: ml
|
|
28
|
+
Requires-Dist: scikit-learn>=1.3; extra == "ml"
|
|
29
|
+
Requires-Dist: numpy>=1.26; extra == "ml"
|
|
30
|
+
Provides-Extra: dev
|
|
31
|
+
Requires-Dist: pytest>=8.0; extra == "dev"
|
|
32
|
+
Requires-Dist: pytest-cov>=5.0; extra == "dev"
|
|
33
|
+
Requires-Dist: ruff>=0.4; extra == "dev"
|
|
34
|
+
Requires-Dist: mypy>=1.10; extra == "dev"
|
|
35
|
+
Requires-Dist: bandit>=1.7; extra == "dev"
|
|
36
|
+
Requires-Dist: pip-audit>=2.7; extra == "dev"
|
|
37
|
+
Dynamic: license-file
|
|
38
|
+
|
|
39
|
+
# JANISSARY
|
|
40
|
+
|
|
41
|
+
**Differential DAST for teams who need results they can trust.**
|
|
42
|
+
|
|
43
|
+
> ### Authorised use only
|
|
44
|
+
>
|
|
45
|
+
> JANISSARY is a dual-use security testing tool. Use it **only**
|
|
46
|
+
> against systems you own, or systems you have prior written
|
|
47
|
+
> permission to test.
|
|
48
|
+
>
|
|
49
|
+
> By running any network command you accept the
|
|
50
|
+
> [Terms of Use](LEGAL.md). Review with `janissary terms show`.
|
|
51
|
+
|
|
52
|
+
[](LICENSE)
|
|
53
|
+
[](https://python.org)
|
|
54
|
+
|
|
55
|
+
---
|
|
56
|
+
|
|
57
|
+
## Why JANISSARY
|
|
58
|
+
|
|
59
|
+
Most DAST tools are either expensive enterprise platforms or raw scripts that produce unusable noise. JANISSARY is different in three specific ways:
|
|
60
|
+
|
|
61
|
+
**Differential detection eliminates false positives by design.** Every finding is gated by a baseline comparison. No finding is ever emitted from a single response alone.
|
|
62
|
+
|
|
63
|
+
**WAF-aware pacing keeps you under the radar.** JANISSARY detects Cloudflare, Akamai, Sucuri, Imperva, AWS WAF, F5, Barracuda, ModSecurity, Wordfence, and Fastly, then backs off on blocks and recovers on clean streaks.
|
|
64
|
+
|
|
65
|
+
**Multi-protocol coverage.** HTTP, XML-RPC, GraphQL, and WebSocket, combined into a single agent run.
|
|
66
|
+
|
|
67
|
+
---
|
|
68
|
+
|
|
69
|
+
## See it work
|
|
70
|
+
|
|
71
|
+

|
|
72
|
+
|
|
73
|
+
One real SQL injection, scanned with `janissary scan`:
|
|
74
|
+
|
|
75
|
+
```text
|
|
76
|
+
$ janissary scan -u "http://localhost:5001/sqli?q=test" -p q
|
|
77
|
+
|
|
78
|
+
[*] Scanning http://localhost:5001/sqli?q=test
|
|
79
|
+
[*] Parameters: q
|
|
80
|
+
[*] Baseline samples: 10
|
|
81
|
+
|
|
82
|
+
[*] Probing for WAF...
|
|
83
|
+
No WAF signatures observed
|
|
84
|
+
[q] baseline is static - timing gates disabled
|
|
85
|
+
[q] sql_single_quote -> CRITICAL: db_error | SQLITE error signature matched
|
|
86
|
+
[q] sql_union_null -> HIGH: status_change | Baseline 200 -> Payload 500
|
|
87
|
+
...
|
|
88
|
+
|
|
89
|
+
============================================================
|
|
90
|
+
SCAN SUMMARY
|
|
91
|
+
============================================================
|
|
92
|
+
Target: http://localhost:5001/sqli?q=test
|
|
93
|
+
Parameters: q
|
|
94
|
+
Method: GET
|
|
95
|
+
Total requests: 29
|
|
96
|
+
Findings: 11 in 2 groups
|
|
97
|
+
|
|
98
|
+
Baselines:
|
|
99
|
+
q: samples=10 mean=2.0484s std=0.0098s stable_body=True
|
|
100
|
+
|
|
101
|
+
Findings:
|
|
102
|
+
F-001 CRITICAL sqli:sql_injection (param=q)
|
|
103
|
+
- [sql_single_quote] db_error: SQLITE error signature matched
|
|
104
|
+
- [sql_single_quote] status_change: Baseline 200 -> Payload 500
|
|
105
|
+
- [sql_single_quote] length_anomaly: Response 3.6x baseline
|
|
106
|
+
- [sql_or_1eq1] length_anomaly: Response 3.8x baseline
|
|
107
|
+
- [sql_union_null] status_change: Baseline 200 -> Payload 500
|
|
108
|
+
- [sql_union_null] length_anomaly: Response 10.1x baseline
|
|
109
|
+
- [sql_sleep_mysql] status_change: Baseline 200 -> Payload 500
|
|
110
|
+
- [sql_sleep_mysql] length_anomaly: Response 3.3x baseline
|
|
111
|
+
- [sql_sleep_pg] status_change: Baseline 200 -> Payload 500
|
|
112
|
+
- [sql_sleep_pg] length_anomaly: Response 5.8x baseline
|
|
113
|
+
|
|
114
|
+
F-002 LOW sqli:reflection (param=q)
|
|
115
|
+
- [sql_single_quote] payload_reflected: Payload reflected (raw)
|
|
116
|
+
|
|
117
|
+
Findings by severity:
|
|
118
|
+
CRITICAL 1
|
|
119
|
+
HIGH 4
|
|
120
|
+
MEDIUM 5
|
|
121
|
+
LOW 1
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
Eleven signals, **one bug**. Every piece of evidence for `F-001` points
|
|
125
|
+
at the same SQL injection, so JANISSARY groups them. `F-002` is a
|
|
126
|
+
different root cause (reflection) and stays separate. One finding to
|
|
127
|
+
triage, with the receipts attached.
|
|
128
|
+
---
|
|
129
|
+
|
|
130
|
+
## Install
|
|
131
|
+
|
|
132
|
+
```bash
|
|
133
|
+
git clone https://github.com/Hetaireia/janissary.git
|
|
134
|
+
cd janissary
|
|
135
|
+
pip install -e .
|
|
136
|
+
```
|
|
137
|
+
|
|
138
|
+
---
|
|
139
|
+
|
|
140
|
+
## Quickstart
|
|
141
|
+
|
|
142
|
+
Accept the Terms of Use (required once before any network command):
|
|
143
|
+
|
|
144
|
+
```bash
|
|
145
|
+
janissary terms accept
|
|
146
|
+
```
|
|
147
|
+
|
|
148
|
+
Scan a single endpoint:
|
|
149
|
+
|
|
150
|
+
```bash
|
|
151
|
+
janissary scan -u "https://target.example/sqli?q=test" -p q
|
|
152
|
+
```
|
|
153
|
+
|
|
154
|
+
Scan a Git repository for leaked credentials:
|
|
155
|
+
|
|
156
|
+
```bash
|
|
157
|
+
janissary creds ./my-repo --scan-git
|
|
158
|
+
```
|
|
159
|
+
|
|
160
|
+
Fingerprint a target:
|
|
161
|
+
|
|
162
|
+
```bash
|
|
163
|
+
janissary fingerprint https://target.example
|
|
164
|
+
```
|
|
165
|
+
|
|
166
|
+
Probe for admin panels:
|
|
167
|
+
|
|
168
|
+
```bash
|
|
169
|
+
janissary admin https://target.example
|
|
170
|
+
```
|
|
171
|
+
|
|
172
|
+
---
|
|
173
|
+
|
|
174
|
+
## Commands
|
|
175
|
+
|
|
176
|
+
| Command | What it does |
|
|
177
|
+
|---|---|
|
|
178
|
+
| `scan` | HTTP scanning: SQLi, XSS, SSRF, traversal, cmdi |
|
|
179
|
+
| `creds` | Credential discovery in tree or Git history |
|
|
180
|
+
| `fingerprint` | CMS and technology identification |
|
|
181
|
+
| `graphql` | GraphQL detection and field enumeration |
|
|
182
|
+
| `ws` | WebSocket recon |
|
|
183
|
+
| `admin` | Admin panel discovery, 18 platforms |
|
|
184
|
+
| `agent` | Orchestrates recon, persists findings |
|
|
185
|
+
| `terms` | Show, check, or accept Terms of Use |
|
|
186
|
+
| `attack sqli-union` | UNION extractor (gated) |
|
|
187
|
+
| `attack nuclei` | Nuclei runner (gated) |
|
|
188
|
+
|
|
189
|
+
Run `janissary --help` for full flags.
|
|
190
|
+
|
|
191
|
+
---
|
|
192
|
+
|
|
193
|
+
## Attack modules
|
|
194
|
+
|
|
195
|
+
The `attack` subcommands are opt-in. They require `--attack-confirm` in addition to the Terms-of-Use gate. Neither alone is enough.
|
|
196
|
+
|
|
197
|
+
- **`attack sqli-union`** - extracts DBMS version, current database, database list, and table list from a vulnerable parameter. Hard limits: 32 columns, 100 rows, 64KB. Aborts on instability.
|
|
198
|
+
- **`attack nuclei`** - shells out to the Nuclei binary, streams JSONL, parses findings. Requires an explicit template list; refuses to run Nuclei's default set.
|
|
199
|
+
|
|
200
|
+
---
|
|
201
|
+
|
|
202
|
+
## Agent
|
|
203
|
+
|
|
204
|
+
The `agent` command ties the recon modules together: fingerprint, detect WAF, consult the platform knowledge base, run applicable modules, persist findings.
|
|
205
|
+
|
|
206
|
+
```bash
|
|
207
|
+
janissary agent https://target.example --attack-confirm
|
|
208
|
+
```
|
|
209
|
+
|
|
210
|
+
---
|
|
211
|
+
|
|
212
|
+
|
|
213
|
+
## Scope, authentication, and machine-readable output
|
|
214
|
+
|
|
215
|
+
### Scope enforcement
|
|
216
|
+
|
|
217
|
+
Hunters run against bug-bounty programs whose scope is contractual.
|
|
218
|
+
`--scope-include` and `--scope-exclude` refuse to touch anything outside
|
|
219
|
+
the declared boundary - before any network I/O, with exit code 64 and an
|
|
220
|
+
empty stdout.
|
|
221
|
+
|
|
222
|
+
```bash
|
|
223
|
+
# Only scan example.com and its subdomains, never admin.example.com
|
|
224
|
+
janissary scan -u "https://api.example.com/v1/items?id=1" -p id \
|
|
225
|
+
--scope-include "*.example.com" \
|
|
226
|
+
--scope-exclude "admin.example.com"
|
|
227
|
+
|
|
228
|
+
# Internal network, CIDR-based
|
|
229
|
+
janissary scan -u "http://10.1.2.3/" -p q --scope-include "10.0.0.0/8"
|
|
230
|
+
```
|
|
231
|
+
|
|
232
|
+
Deny always beats allow. Pattern syntax: `example.com`, `*.example.com`,
|
|
233
|
+
`10.0.0.0/8`, `10.0.0.5`, `/api/`, `https://api.example.com/v1/`, or `*`
|
|
234
|
+
for any. If no `--scope-include` is given, everything passes the include
|
|
235
|
+
check; excludes still apply.
|
|
236
|
+
|
|
237
|
+
### Authentication
|
|
238
|
+
|
|
239
|
+
Static cookie and bearer-token headers apply to every request in the scan:
|
|
240
|
+
WAF probes, preflight, baselines, and payloads.
|
|
241
|
+
|
|
242
|
+
```bash
|
|
243
|
+
janissary scan -u "https://app.example.com/profile?id=1" -p id \
|
|
244
|
+
--cookie "session=abc123; csrf=xyz"
|
|
245
|
+
|
|
246
|
+
janissary agent https://app.example.com --attack-confirm \
|
|
247
|
+
--bearer "eyJhbGciOi..."
|
|
248
|
+
```
|
|
249
|
+
|
|
250
|
+
`--redact-auth` swaps `Authorization` and `Cookie` header values with
|
|
251
|
+
`[REDACTED]` in JSON/JSONL output only. Body content is untouched - a
|
|
252
|
+
leaked secret inside a response body is often the actual bug. Use this
|
|
253
|
+
before pasting scan output into a bug report.
|
|
254
|
+
|
|
255
|
+
### Machine-readable output
|
|
256
|
+
|
|
257
|
+
`--json` emits one envelope document to stdout. `--jsonl` emits one
|
|
258
|
+
finding per line. Both reserve stdout for the machine payload; every
|
|
259
|
+
human status line (progress, WAF feedback, backoff) goes to stderr.
|
|
260
|
+
`--quiet` silences stderr only - it never affects stdout.
|
|
261
|
+
|
|
262
|
+
```bash
|
|
263
|
+
# One document, all findings
|
|
264
|
+
janissary scan -u "https://target.example/?q=1" -p q --json > scan.json
|
|
265
|
+
|
|
266
|
+
# Streaming, filter with jq
|
|
267
|
+
janissary scan -u "https://target.example/?q=1" -p q --jsonl | jq -c .
|
|
268
|
+
```
|
|
269
|
+
|
|
270
|
+
Every finding carries `raw_request` and `raw_response` as HTTP/1.1 text
|
|
271
|
+
with CRLF line endings, ready to paste into Burp Repeater.
|
|
272
|
+
|
|
273
|
+
---
|
|
274
|
+
|
|
275
|
+
## Contributing
|
|
276
|
+
|
|
277
|
+
See [CONTRIBUTING.md](CONTRIBUTING.md).
|
|
278
|
+
|
|
279
|
+
## Security
|
|
280
|
+
|
|
281
|
+
See [SECURITY.md](SECURITY.md).
|
|
282
|
+
|
|
283
|
+
## License
|
|
284
|
+
|
|
285
|
+
Apache 2.0 for the source code. See [LICENSE](LICENSE).
|
|
286
|
+
|
|
287
|
+
Use is additionally governed by the [Terms of Use](LEGAL.md), which supplement and do not replace the Apache 2.0 licence.
|