What is shiro-attack2?

A command-line security tool for testing Apache Shiro applications affected by the Shiro-550 remember-me deserialization vulnerability, also known as CVE-2016-4437. Deserialization is the process of turning stored data back into objects, which can be unsafe when untrusted data is accepted.

It supports single-target checks, key testing, gadget-chain detection, command execution, memory-resident payload injection, and changing the application key.

It helps security testers determine whether a Shiro application is exposed and assess the impact of that vulnerability.

shiro-attack2 — Plugin by SummerSec

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Claude Code

/plugin marketplace add SummerSec/ShiroAttack2

agentmods

npx agentmods add plugins/summersec/shiroattack2/marketplace

Clone the repo

git clone --depth 1 https://github.com/SummerSec/ShiroAttack2

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

shiro-attack2 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude-plugin/marketplace.json · 21 lines

What it actually says

{
  "name": "shiro-attack2",
  "description": "Apache Shiro rememberMe 反序列化漏洞 (Shiro-550, CVE-2016-4437) 利用工具 — 密钥爆破、Gadget 链探测、命令执行、内存马注入、Key 修改。",
  "owner": {
    "name": "SummerSec",
    "url": "https://github.com/SummerSec"
  },
  "plugins": [
    {
      "name": "shiro-attack-cli",
      "description": "Apache Shiro-550 漏洞利用 CLI：单目标探测、密钥爆破、Gadget 链自动检测、命令执行、内存马注入、Key 修改。",
      "version": "5.1.1",
      "source": "./skills/shiro-attack-cli",
      "author": {
        "name": "SummerSec",
        "url": "https://github.com/SummerSec"
      }
    }
  ]
}

Files

What ships with it

1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

plugin.json 287 B

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 21 lines scan A b4a503585681

Subscribe to this mod's changes

shiro-attack2 is a plugin published in the GitHub repository SummerSec/ShiroAttack2 (2,621 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Memory and context Security Testing shiro shiro-security shiro550 shiroexp

shiro-attack2

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What ships with it

What this file has done since we first saw it

Other plugins, from other repositories

nextjs

nextjs

claude-plugins-official

knowledge-work-plugins

ecc

ecc