mandiant / adfspoof Goto Github PK

Is this still valid? Got everything done, except having issue with the O365 template/output. If this is still valid, I'll put the head down and "keep trying".

Awesome work--great research and more people need to talk about ADFS, SAML 2.0, misplaced trust, etc..

Keep getting a:
AADSTS90013 error

Note: I dumped the ADFS properly (thanks). Decoded where i needed to, converted to Hex where needed. ADFSpoof with o365 gives me a great output.

It's just using Burp now with the provided output of ADFSpoof which is causing the issue.

Hello,
Thanks for this interesting job! I was not there during the presentation and this may explain my question ;-)

With ADFSDump, I extracted the Encrypted Signing Key (Encrypted_pfx) from the database in this format: AAAAAQAAAAA....
And the DKM Private Key in this format 9F-D2-85-5F-D6-EF-D9-15-22-21-EC-5E-45-9E-5C-DF-25-BB-0B-B4-....

I understand that i need to convert both in bin format. The first one from base 64. But I dont kwow for the second one (The DKM Key)...?

I think this is my problem because when i tried to lauch python3 ADFSpoof.py -b pfx.bin key.txt dump i encounter the Calculated MAC did not match anticipated MAC error.

I will really appreciate your help.

Rémi

Running setup.py install for restructuredtext-lint ... done
Running setup.py develop for cryptography
ERROR: Command errored out with exit status 1:
command: 'c:\users\hemant\appdata\local\programs\python\python39\python.exe' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\Hemant\Downloads\cryptography-master\cryptography-master\setup.py'"'"'; file='"'"'C:\Users\Hemant\Downloads\cryptography-master\cryptography-master\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' develop --no-deps
cwd: C:\Users\Hemant\Downloads\cryptography-master\cryptography-master
Complete output (20 lines):
running develop
running egg_info
writing src\cryptography.egg-info\PKG-INFO
writing dependency_links to src\cryptography.egg-info\dependency_links.txt
writing requirements to src\cryptography.egg-info\requires.txt
writing top-level names to src\cryptography.egg-info\top_level.txt
reading manifest file 'src\cryptography.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching 'docs_build'
warning: no previously-included files matching '*' found under directory 'vectors'
writing manifest file 'src\cryptography.egg-info\SOURCES.txt'
running build_ext
generating cffi module 'build\temp.win-amd64-3.9\Release\_padding.c'
creating build
creating build\temp.win-amd64-3.9
creating build\temp.win-amd64-3.9\Release
generating cffi module 'build\temp.win-amd64-3.9\Release\_constant_time.c'
generating cffi module 'build\temp.win-amd64-3.9\Release\_openssl.c'
building '_openssl' extension
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
----------------------------------------
ERROR: Command errored out with exit status 1: 'c:\users\hemant\appdata\local\programs\python\python39\python.exe' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\Hemant\Downloads\cryptography-master\cryptography-master\setup.py'"'"'; file='"'"'C:\Users\Hemant\Downloads\cryptography-master\cryptography-master\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' develop --no-deps Check the logs for full command output.

When running python ADFSpoof.py -b Token_sign_blob.bin DKMkey.bin dump
I am getting "Version should be 1" message and script dies.
I modified EncryptedPfx.py to output what the actual version is. The version is: "538976257"
Probably the problem lies in the way I saved EncryptedPfx and DKMkey from ADFSDump
What I did:

1. EncryptedPfx
   a) I took everything between: [-] Encrypted Token Signing Key Begin and [-] Encrypted Token Signing Key End, which looks like this:
   AAAAAQAAAAAEEGXuqoRBIwFInUU[....]q6YTotIB2BA8v+zfmKuMDPw==
   b) I based64 decoded and saved the output to Token_sign_blob.bin

2. DKM key
   a) I took Private Key: B7-12-96-C1-50-89-CA-54-B7-D2-ED-E5-F0-8E-24-AA-4F-27-2F-1B-2C-9E-2E-8A-43-47-42-FD-55-B0-72-CB
   b) I removed dashes.
   c) I base64 decoded it and saved the output to DKMkey.bin

Is there any other type of conversation that needs to be done?

Look like the use of an unstable and unmaintain fork of cryptography shows its limit.
It's impossible to build the fork with OpenSSL3.0 which is now the default version installed.
It's a pity

Running ADFSpoof generates the token as expected but when replacing the 'wresult' parameter in an authentication flow (through burp) I keep getting the "AADSTS50107: The requested federation realm object does not exist" error.

The generated token look nearly identical to the one that is created by ADFS - I saw another issue that stated that now you have to go through the entire login process as the login.srf request should contain all the headers to the server as opposed to just sending a request with the token (like on the video from RT19) so I wonder if anything else was change that causes the error I am experiencing?

Informative:

• key is converted to binary format
• signing token is decoded with base64 and saved to a file (it looks like the expected binary format as well)

Hi, It's a nice work.
When i ran it on adfs server it outputted two private key like this:

[-] Private Key: F1-5A-5F-C0-26-29-80-07-E1-FC-C4-70-2C-12-BB-C5-28-04-42-A4-35-62-90-07-B1-D0-CA-7D-26-ED-F6-95

[-] Private Key: DD-AD-55-55-B6-50-21-BA-7E-B2-97-33-B5-42-58-4C-D3-3D-A6-AD-AC-30-0C-30-CD-83-5D-0E-62-BC-CC-ED

Why did this happen? Witch key is correct?