KitPloit - PenTest Tools!
jwtXploiter - A Tool To Test Security Of Json Web Token

https://1.bp.blogspot.com/-vVZWi21UEPg/YRIRLVR7hHI/AAAAAAAAptA/vNcIKhL3VPo8xxG94bshOO2va9h5n7pBwCNcBGAsYHQ/w640-h466/jwt-crack.png A tool to test security of JSON Web Tokens. Test a JWT against all known CVEs;

* Tamper with the token payload: changes claims and subclaims values.
* Exploit known vulnerable header claims (kid, jku, x5u)
* Verify a token
* Retrieve the public key of your target's ssl connection and try to use it in a key confusion attack with one option only
* All JWAs supported
* Generates a JWK and insert it in the token header
* And much, much more! Wiki* Read the wiki! wiki InstallationN.B. Cloning the repository should be avoided except for development purposes! N.B. Deb package has to be considered beta

*
With rpm: wget http://andreatedeschi.uno/jwtxploiter/jwtxploiter-1.2.1-1.noarch.rpm
sudo rpm --install jwtxploiter-1.2.1-1.noarch.rpmor, if previous version is installed on your machine sudo rpm --upgrade jwtxploiter-1.2.1-1.noarch.rpm*
With pip: sudo pip install jwtxploiter*
With deb: wget http://andreatedeschi.uno/jwtxploiter/jwtxploiter_1.2.1-1_all.deb
sudo dpkg -i jwtxploiter_1.2.1-1_all.deb*
Cloing the repo: git clone https://github.com/DontPanicO/jwtXploiter.git
./install.shN.B. python3-pip package is required to install dependencies, be sure to have it installed. Who this tool is written for?*
Web Application Penetration Tester / Bug Bounty Hunters

* This tool has been written with the aim of become a key part of pentesters toolkit.

*
Devs who need to test the secuirty of JWTs used in their applications

*
CTF Players

*
Not For Students

* Since this tool automates lot of stuff, without force the user to know what's happening under the hood, it won't help you to understand the vulnerabilities it exploits. To Know*
For attacks that generates a jwks file, you could find it in the current working directory. Remeber to deletes such files in order to avoid conflicts.

*
For jku/x5u injection that needs to merge two urls (the server vulnerable url and your one), the HERE keyword is required.

*
For redirect attacks the keyword should replace the redirect url, e.g.

* http://app.com/foo?redirect=bar&some=thing --> http://app.com/foo?redirect=HERE&some=thing

*
For jku/x5u injections via HTTP header injection attacks, the HERE keyword sould be appended to the vulnerable parameter, without replacing its value, e.g.

* http://app.com/foo?param=value --> http://app.com/foo?param=valueHERE

*
Also, in such cases, be sure to pass the server url and your one as comma separated values.

*
'/.well-known/jwks.json' is automatically appended to your url in jku/x5u attacks. So make sure to place the jwks file under this path on your server.

*
If you don't want that happen, use the --manual option, but this option is compatible only with --jku-basic and --x5u-basic so, you will need to manually craft the url and pass it to those options, even for attacks that exploit Open Redirect or HTTP header injection.

*
Look at the wiki for a detailed documentation. Download jwtXploiter

Hacking on Medium
Crypto Heist

https://cdn-images-1.medium.com/max/800/0*MmwnehV1a4-UF73m.png
Crypto has been the most popular financial instrument in the past few years, especially during the COVID-19 pandemic.

Continue reading on invstr »

Hacking on Medium
Space challenge PWN — HTB

https://cdn-images-1.medium.com/max/753/1*Cw_jxP7_DUWRj_Ie_t6n3g.jpeg
Walkthrough includes— Buffer overflow, ROP, and shell coding.

Continue reading on Medium »

Hacking on Medium
Taking Over Employee Accounts by Managers with Zero Employee Interaction

https://cdn-images-1.medium.com/max/1564/1*44fj4eIWUAn1IhEeGJC18g.png
Hello,

Continue reading on Medium »

Taking Over Employee Accounts by Managers with Zero Employee Interaction

Hello,Continue reading on Medium »
Read more...

Black Hat Ethical Hacking
Microsoft Warns: Another Unpatched PrintNightmare Zero-Day

https://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Microsoft Warns: Another Unpatched PrintNightmare Zero-DayPost Views: 141
Reading Time: 1 Minute
One day after dropping its scheduled August Patch Tuesday update, Microsoft issued a warning about yet another unpatched privilege escalation/remote code-execution (RCE) vulnerability in the Windows Print Spooler.
The zero-day bug, tracked as CVE-2021-36958, carries a CVSS vulnerability-severity scale rating of 7.3, meaning that it’s rated as “important.” Microsoft said that it allows for a local attack vector requiring user interaction, but that the attack complexity is low, with few privileges required.

“A remote code-execution vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations,” the computing giant explained in its Wednesday advisory. “An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change or delete data; or create new accounts with full user rights.”

The CERT Coordination Center actually flagged the issue in mid-July, when it warned that a working exploit was available. That proof-of-concept (PoC), issued by Benjamin Delpy, comes complete with a video.
So apparently @offenseindepth reported this to Microsoft before your public PoC on July 17?
And Microsoft is only just now publishing an out-of-band bulletin on it on August 11?
https://s.w.org/images/core/emoji/13.1.0/72x72/1f914.png pic.twitter.com/8eDHD7tg7A

— Will Dormann (@wdormann) August 11, 2021
See Also: Auth Bypass Bug Exploited, Affecting Millions of Routers On Thursday, CERT/CC issued more details on the issue, explaining that it arises from an oversight in signature requirements around the “Point and Print” capability, which allows users without administrative privileges to install printer drivers that execute with SYSTEM privileges via the Print Spooler service.

While Microsoft requires that printers installable via Point are either signed by a WHQL release signature or by a trusted certificate, Windows printer drivers can specify queue-specific files that are associated with the use of the device, which leaves a loophole for malicious actors.

“For example, a shared printer can specify a CopyFiles directive for arbitrary files,” according to the CERT/CC advisory. “These files, which may be copied over alongside the digital-signature-enforced printer driver files, are not covered by any signature requirement. Furthermore, these files can be used to overwrite any of the signature-verified files that were placed on a system during printer driver install. This can allow for local privilege escalation to SYSTEM on a vulnerable system.”
See Also: Offensive Security Tool: Mimikatz Microsoft credited Victor Mata of FusionX at Accenture Security with originally reporting the issue, which Mata said occurred back in December 2020:
Hey guys, I reported the vulnerability in Dec'20 but haven't disclosed details at MSRC's request. It looks like they acknowledged it today due to the recent events with print spooler.

— Victor Mata (@offenseindepth) August 11, 2021
So far, Microsoft hasn’t seen any attacks in the wild using the bug, but it noted that exploitation is “more likely.” With a working exploit in circulation, that seems a fair assessment. Print Spooler-Palooza and the PrintNightmareDelpy characterized this latest zero-day as being part of the string of Print Spooler bugs collectively known as PrintNightmare.

The bad dream started in early[...]

Black Hat Ethical Hacking
Offensive Security Tool: Warcannon

https://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Offensive Security Tool: WarcannonPost Views: 143 https://www.blackhatethicalhacking.com/wp-content/uploads/2020/11/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-8-1-300x120.png Support our work or become a Patron and find exclusive video content available ONLY on Patreon showing you continuous techniques and methodologies in Offensive Security.
Reading Time: 6 Minutes

Offensive Security Tool: Warcannon GitHub Link WARCannon – Catastrophically powerful parallel WARC processingWarcannon by C6fc, is an open source tool that makes grepping the internet for web vulnerabilities simpler, faster and cheaper. It was unveiled at Black Hat USA event 2021. Security researchers and bug bounty hunters who unearth novel flaws in web applications, web frameworks, or open source components can use WARCannon to non-invasively test regex patterns across the entire internet for corresponding vulnerability indicators. Fed by Common Crawl spiders’ trove of JavaScript, CSS, and other website code, WARCannon tackles this challenge with parallel WARC processing across hundreds of CPU cores, while costs are reduced courtesy of spot fleets and same-region data transfer.
With WARCannon, you can:

* Build and test regex patterns against real Common Crawl data
* Easily load Common Crawl datasets for parallel processing
* Scale compute capabilities to asynchronously crunch through WARCs at frankly unreasonable capacity.
* Store and easily retrieve the results How it WorksWARCannon leverages clever use of AWS technologies to horizontally scale to any capacity, minimize cost through spot fleets and same-region data transfer, draw from S3 at incredible speeds (up to 100Gbps per node), parallelize across hundreds of CPU cores, report status via DynamoDB and CloudFront, and store results via S3.

In all, WARCannon can process multiple regular expression patterns across 400TB in a few hours for around $100. InstallationWARCannon requires that you have the following installed:

* awscli (v2)
* terraform (v0.11)
* jq
* jsonnet
* npm (v12 or v14)

ProTip: To keep things clean and distinct from other things you may have in AWS, it’s STRONGLY recommended that you deploy WARCannon in a fresh account. You can create a new account easily from the ‘Organizations’ console in AWS. By ‘STRONGLY recommended’, it means ‘seriously don’t install this next to other stuff’.
First, clone the repo and copy the example settings.
$ git clone git@github.com:c6fc/warcannon.git $ cd warcannon warcannon$ cp settings.json.sample settings.json
Edit settings.json to taste:

backendBucket: Is the bucket to store the terraform state in. If it doesn’t exist, WARCannon will create it for you. Replace ‘< somerandomcharacters >’ with random characters to make it unique, or specify another bucket you own.

awsProfile: The profile name in ~/.aws/credentials that you want to piggyback on for the installation.

nodeInstanceType: An array of instance types to use for parallel processing. ‘c’-types are best value for this purpose, and any size can be used. [“c5n.18xlarge”] is the recommended value for true campaigns.

nodeCapacity: The number of nodes to request during parallel processing. The resulting nodes will be an arbitrary distribution of the nodeInstanceTypes you specify.

nodeParallelism: The number of simultaneous WARCs to process per vCPU. 2 is a good number here. If nodes have insufficient RAM to run at this level of parallelism (as you might encounter with ‘c’-type instances), they’ll run at the highest safe parallelism instead.

nodeMaxDuration: The maximum lifespan of compute nodes in seconds. Nodes will be automatically t[...]

erminated after this time if the job has still not completed. Default value is 24 hours.

sshPubkey: A public SSH key to facilitate remote access to nodes for troubleshooting.

allowSSHFrom: A CIDR mask to allow SSH from. Typically this will be <yourpublicip/32 Grepping the InternetWARCannon is fed by Common Crawl via the AWS Open Data program. Common Crawl is unique in that the data retrieved by their spiders not only captures website text, but also other text-based content like JavaScript, TypeScript, full HTML, CSS, etc. By constructing suitable Regular Expressions capable of identifying unique components, researchers can identify websites by the technologies they use, and do so without ever touching the website themselves. The problem is that this requires parsing hundreds of terabytes of data, which is a tall order no matter what resources you have at your disposal. Developing Regular ExpressionsGrepping the internet isn’t for the faint of heart, but starting with an effective seive is the first start. WARCannon supports this by enabling local verification of regular expressions against real Common Crawl data. First, open lambda_functions/warcannon/matches.js and modify the regex_patterns object to include the regular expressions you wish to use in name: pattern format. Here’s an example from the default search set:

exports.regex_patterns = {
“access_key_id”: /(\’A|”A)(SIA|KIA|IDA|ROA)[JI][A-Z0-9]{14}[AQ][\'”]/g,
};
Strings matching this expression will be saved under the corresponding key in the results; access_key_id in this case.

Protip: Use RegExr with the ‘JavaScript’ format to build and test regular expressions against known-good matches.

You also have the option of only capturing results from specified domains. To do this, simply populate the domains array with the FQDNs that you wish to include. It is recommended that you leave this empty [] since it’s almost never worthwhile (the processing effort saved is very small), but it can be useful in some niche cases.

exports.domains = [“example1.com”, “example2.com”];

Once the matches.js is populated, run the following command:

warcannon$ ./warcannon testLocal warc_path>
WARCannon will then download the warc and parse it with your configured matches. There are a few quality-of-life things that WARCannon does by default that you should be aware of:

1. WARCannon will download the warc to /tmp/warcannon.testLocal on first run, and will re-use the downloaded warc from then on even if you change the warc_path. If you wish to use a different warc, you must delete this file.
2. WARCs are large; most coming in at just over 1GB. WARCannon uses the CLI for multi-threaded downloads, but if you have slow internet, you’ll need to exercise patience the first time around.
On top of everything else, WARCannon will attempt to evaluate the total compute cost of your regular expressions when run locally. This way, you can be informed if a given regular expression will significantly impact performance before you execute your campaign.

https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/687474703a2f2f633666632e696f2f77617263616e6e6f6e2d6465762e706e67.png Performing Custom ProcessingSometimes a simple regex pattern isn’t sufficient on its own, and you need some additional steps to ensure you’re returning the right information. In this case, simply adding a function to the exports.custom_functions object with the same key name allows you to perform any additional processing you see fit.

exports.regex_patterns = {
“access_key_id”: /(\’A|”A)(SIA|KIA|IDA|ROA)[JI][A-Z0-9]{14}[AQ][\'”]/g,
};

exports.custom_functions = {
“access_key_id”: function(match) {
// Ignore matches with ‘EXAMPLE’ in the text, since this is common for documentation.
if (match.text(/EXAMPLE/) != null) {
// Returning a boolean ‘false’ discards the match.
return false
}
}
}
Note: WARCannon is meant to crunch through text at stupid[...]

speeds. While it’s certainly possible to perform any type of operation you’d like, adding high-latency custom functions such as network calls can significantly increase processing time and costs. Network calls could also result in LOTS of calls against a website, which could get you in trouble. Be smart about how you use these functions. Performing a One-Off Test in AWSThe costs of AWS can be anxiety-inducing, especially when you’re only looking to do some research. WARCannon is built to allow both one-off executions in addition to full campaigns, so you can be confident in the results you’ll get back. Once you’re happy with the results you get with testLocal, you can deploy your updated matches and run a cloud-backed test easily:

warcannon$ ./warcannon deploy
warcannon$ ./warcannon test warc_path>

This will synchronously execute a Lambda function with the regular expressions you’ve configured, and immediately return the results. This process takes about 2.5 minutes, so don’t be afraid to wait while it does its magic. Launching a Real CampaignOnce you’re happy with the results you get in Lambda, you’re ready to grep the internet for real. We’ll first go over some basic housekeeping, then kick it off. Clearing the QueueWARCannon uses AWS Simple Queue Service to distribute work to the compute nodes. To ensure that your results aren’t tainted with any prior runs, you can tell WARCannon to empty the queue:

warcannon$ ./warcannon emptyQueue
[+] Cleared [ 15 ] messages from the queue

You can then verify the state of the queue:

warcannon$ ./warcannon status
Deployed: [ YES ]; SQS Status: [ EMPTY ]
Job Status: [ INACTIVE ]
Active job url: https://d201offlnmhkmd.cloudfront.net

Verify the following before proceeding:

1. The SQS Queue is empty
2. The job status is ‘INACTIVE’ Populating the Queue (Simple)In order to create the queue messages that the compute nodes will consume, you must first populate SQS with crawl data. WARCannon has several commands to help with this, starting with the ability to show the available scans. In this case, let’s look at the scans available for the year 2021:

warcannon$ ./warcannon list 2021
CC-MAIN-2021-04
CC-MAIN-2021-10

We have two scans matching the string “2021” to work with. We can now instruct WARCannon to populate the queue based on one of these scans. This time, we need to provide a parameter that uniquely identifies one of the scans. “2021-04” will do the trick. We could choose to populate only a partial scan by also specifying a number of chunks and a chunk size, but we’ll skip that for now.
warcannon$ ./warcannon populate 2021-04
{Created 799 chunks of 100 from 79840 available segments“
“StatusCode“: 200,
“ExecutedVersion“: “$LATEST“
}
See Also: Microsoft Warns: Another Unpatched PrintNightmare Zero-Day Populating the Queue via Athena (Advanced)During deployment, WARCannon automatically provisions a database (warcannon_commoncrawl) and workgroup (warcannon) in Athena that can be used to rapidly query information from CommonCrawl. This can be especially useful for populating sparse campaigns based on certain queries. For example, the following query will search for WARCs that contain responses from ‘example.com’

SELECT
warc_filename,
COUNT(url_path) as num
FROM
warcannon_commoncrawl.ccindex
WHERE
subset = ‘warc’ AND
url_host_registered_domain IN (‘example.com’) AND
crawl = ‘CC-MAIN-2021-04’
GROUP BY warc_filename
ORDER BY num DESC

You can use the Athena console to fine-tune your results, but you must run the query from the WARCannon command line if you intend to populate a job with it:

./warcannon queryAthena “SELECT warc_filename, COUNT(url_path) as num FROM warcannon_commoncrawl.ccindex WHERE subset = ‘warc’ AND url_host_registered_domain IN (‘example.com’) AND crawl = ‘CC-MAIN-2021-04’ GROUP BY warc_filename ORDER BY num DESC”

[+] Query Exec Id: 0319486e-1846-491c-badf-2e23ae213974 .. S[...]

UCCEEDED
WARCannon can then use the results of a query to populate the queue, and does so based on the warc_filename column from the resultset. As such, it’s recommended that you either group by this column or use distinct() to avoid duplicates. WARCannon will throw an error if this field isn’t present. Populate the queue with Athena results by passing the Query Execution ID to the populateAthena command.

./warcannon populateAthena 0319486e-1846-491c-badf-2e23ae213974

{Created 26 chunks of 10 from 251 available segments“
“StatusCode“: 200,
“ExecutedVersion“: “$LATEST“
}
Note: While populating a sparse job for a single domain might seem like a good idea, it often isn’t. The responses from a single domain tend to be spread widely across a large subset of WARCs. This can be seen clearly using the example query above to see that of the ~150,000 records in each WARC, the largest single hit for moderate-sized websites can be in the single-digits. Firing the WARCannonWith the queue populated, we’re ready to fire. WARCannon will do a few sanity checks to ensure everything is in order, then show you the configuration of the campaign and give you one last opportunity to abort before you finalize the order.

warcannon$ ./warcannon fire
[!] This will request [ 6 ] spot instances of type [ m5n.24xlarge, m5dn.24xlarge ]
lasting for [ 86400 ] seconds.

To change this, edit your settings in settings.json and run ./warcannon deploy
—> Ready to fire? [Yes]:

Pull the trigger by responding with ‘Yes’.

—> Ready to fire? [Yes]: Yes
{
“SpotFleetRequestId”: “sfr-03dd32b8-51f7-4c8e-802b-a702fc3c8c95”
}

[+] Spot fleet request has been sent, and nodes should start coming online within ~5 minutes.
Monitor node status and progress at https://d201offlnmhkmd.cloudfront.net
The response includes a link to your unique status URL, where you can monitor the progress of your campaign and the performance of each node.

https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/687474703a2f2f633666632e696f2f77617263616e6e6f6e2d70726f67726573732e706e67.png Obtaining ResultsWARCannon results are stored in S3 in JSON format, broken down by each node responsible for producing the results. Athena results are stored in the same bucket under the /athena/ prefix. You can sync the results of a campaign to the ./warcannon/results/ folder on your local machine using the syncResults command.

./warcannon syncResults

sync: s3://warcannon-results-202…
sync: s3://warcannon-results-202…
sync: s3://warcannon-results-202…
…

You can then empty the results buckets with clearResults

./warcannon clearResults

delete: s3://warcannon-results-202…
delete: s3://warcannon-results-202…
delete: s3://warcannon-results-202…
…
[+] Deleted [ 21 ] files from S3.
See Also: Offensive Security Tool: Mimikatz Recent Tools* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/2-7-90x90.png Offensive Security Tool: Mimikatz7 days ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/07/Screenshot_20210729_145513-90x90.png Offensive Security Tool: Ruler2 weeks ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/07/VoIPsniffer-90x90.png Offensive Security Tool: VoIPmonitor Sniffer3 weeks ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/07/57177630ce750eb1ad40649424d04b9c-90x90.jpeg Offensive Security Tool: Veil4 weeks ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/07/Untitled-design-90x90.png Offensive Security Tool: It Was All A Dream (Windows Print Spooler RCE)1 month ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/07/unknown-e1625210118591-90x90.png Offensive Security Tool: GoSpider1 month ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/06/3Gn0bEI-e1624621931936-90x90.png Offensive Security Tool: Pixload2 months ago
[...]

* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/06/Vqwdgis-90x90.png Offensive Security Tool: SecretFinder2 months ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/06/3v1wot9-90x90.png Offensive Security Tool: CloudFail2 months ago
* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/06/Screenshot_2021-06-04_053854-90x90.png Offensive Security Tool: Pacu – The Amazon Web Services Exploitation Framework2 months ago
style="display:block; text-align:center;"
data-ad-layout="in-article"
data-ad-format="fluid"
data-ad-client="ca-pub-6620833063853657"
data-ad-slot="4517761481">
The post Offensive Security Tool: Warcannon first appeared on Black Hat Ethical Hacking.

jwtXploiter - A Tool To Test Security Of Json Web Token
http://www.kitploit.com/2021/08/jwtxploiter-tool-to-test-security-of.html

A tool to test security of JSON Web Tokens. Test a JWT against all known CVEs; Tamper with the token payload: changes claims and subclaims values. Exploit known vulnerable (https://www.kitploit.com/search/label/Vulnerable) header claims (kid, jku, x5u) Verify a token Retrieve the public key of your target's ssl connection and try to use it in a key confusion attack with one option only All JWAs supported Generates a JWK and insert it in the token header And much, much more!
Wiki
Read the wiki! wiki (https://github.com/DontPanicO/jwtXploiter/wiki)
Installation
N.B. Cloning the repository should be avoided except for development purposes! N.B. Deb package has to be considered beta With rpm: wget http://andreatedeschi.uno/jwtxploiter/jwtxploiter-1.2.1-1.noarch.rpm
sudo rpm --install jwtxploiter-1.2.1-1.noarch.rpm or, if previous version is installed on your machine sudo rpm --upgrade jwtxploiter-1.2.1-1.noarch.rpm With pip: sudo pip install jwtxploiter With deb: wget http://andreatedeschi.uno/jwtxploiter/jwtxploiter_1.2.1-1_all.deb
sudo dpkg -i jwtxploiter_1.2.1-1_all.deb Cloing the repo: git clone https://github.com/DontPanicO/jwtXploiter.git
./install.sh N.B. python3-pip package is required to install dependencies, be sure to have it installed.
Who this tool is written for?
Web Application Penetration Tester / Bug Bounty Hunters This tool has been written with the aim of become a key part of pentesters (https://www.kitploit.com/search/label/Pentesters) toolkit. Devs who need to test the secuirty of JWTs used in their applications CTF Players Not For Students Since this tool automates lot of stuff, without force the user to know what's happening under the hood, it won't help you to understand the vulnerabilities (https://www.kitploit.com/search/label/vulnerabilities) it exploits.
To Know
For attacks that generates a jwks file, you could find it in the current working directory. Remeber to deletes such files in order to avoid conflicts. For jku/x5u injection (https://www.kitploit.com/search/label/Injection) that needs to merge two urls (the server vulnerable url and your one), the HERE keyword is required. For redirect attacks the keyword should replace the redirect url, e.g. http://app.com/foo?redirect=bar&some=thing --> http://app.com/foo?redirect=HERE&some=thing For jku/x5u injections via HTTP header injection attacks, the HERE keyword sould be appended to the vulnerable parameter, without replacing its value, e.g. http://app.com/foo?param=value --> http://app.com/foo?param=valueHERE Also, in such cases, be sure to pass the server url and your one as comma separated values. '/.well-known/jwks.json' is automatically appended to your url in jku/x5u attacks. So make sure to place the jwks file under this path on your server. If you don't want that happen, use the --manual option, but this option is compatible only with --jku-basic and --x5u-basic so, you will need to manually craft the url and pass it to those options, even for attacks that exploit Open Redirect (https://www.kitploit.com/search/label/Open%20Redirect) or HTTP header injection. Look at the wiki for a detailed documentation.

Download jwtXploiter (https://github.com/DontPanicO/jwtXploiter)