agentleFS
NoorQureshiNoorQureshi/SploitAgent/skills/api/api-grpc/SKILL.md

api-grpc

Skill26 starsChanged 31 days agoMITView on GitHub

Test gRPC / Protocol Buffers APIs — reflection, method enumeration, authz, and injection. Load on gRPC services (HTTP/2, content-type application/grpc, .proto files, ports like 50051), grpc-web, or "protobuf". Signals: grpc, protobuf, reflection service, ServerReflection.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Call a method your role shouldn't reach, read/modify another object, or land an injection — proving per-method authz or input handling is …

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

gRPC / Protobuf API attacks

When it applies

The target exposes gRPC (or grpc-web). Binary framing over HTTP/2 makes it feel opaque, but the same authz/injection bugs apply — and server reflection often hands you the whole API.

Why it works

gRPC methods are RPCs with typed messages; security still lives per-method. Reflection (if on) exposes every service/method, and teams frequently skip auth on internal-looking RPCs or trust the client-generated stubs to enforce access.

Method

  1. Enumerate via reflection: grpcurl -plaintext host:50051 list then list <service> and describe <method>; grpcui for an interactive UI. No reflection? Recover .proto from the client/mobile app or JS (grpc-web).
  2. Call methods directly: grpcurl -d '{"id":123}' host:port pkg.Service/Method — test BOLA/BFLA by calling privileged methods or swapping object ids with a low-priv token.
  3. Auth testing: replay with/without metadata (the gRPC equivalent of headers/tokens); many servers authenticate the connection but not each method.
  4. Injection: message fields feed backends — test SQLi/NoSQLi/command injection in string fields.
  5. grpc-web: it rides HTTP/1.1+base64 — proxy through Burp, decode frames, tamper.

Gotchas

  • Reflection off ≠ safe — extract the schema from clients; then grpcurl with a local .proto.
  • Binary framing hides bugs from scanners; manual method-by-method testing is the win.
  • HTTP/2 + TLS: use -plaintext only when the service is plaintext; otherwise pass certs.

Verify success

Call a method your role shouldn't reach, read/modify another object, or land an injection — proving per-method authz or input handling is broken.

References

grpcurl/grpcui docs; OWASP API Security (2023); "hacking gRPC" write-ups.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.