Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update README.md #2

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update README.md #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,11 +10,11 @@ Instagram use AES256-GCM to encrypt the password in this with an 12 byte IV and
We can see the current Instagram encryption configurations at this [endpoint](https://www.instagram.com/data/shared_data/).
For example:
```json
"encryption": {
"key_id": "251",
"public_key": "64c25328c4ba5e40f4e249310b861aa616488e096d4de6f2018c3c33c5e6d75c",
"version": "10"
}
{
"key_id": "0",
"public_key": "c5c457c3651d97dab8ed08fb2004555cfd2143bc5ce69ed4ac196fe9545faa48",
"version": "10"
}
```

This is a ciphertext example:
Expand Down Expand Up @@ -77,7 +77,7 @@ pl = (len(c) - 136 - pad - pad1 - pad2)
print(pl)
```

# Impact
# Impact
To exploit this you need to read the comminication between the client and server.
I have imaginad three possibile scenario:
1. An attacker have physical access to the victim machine
Expand Down