⚡Megatron LLM Hub
←Back to search
Twitter

研究者公开用低成本 LLM 做漏洞挖掘时的提示词与推理过程。

在无前沿模型权限或预算受限时,提示词设计仍显著影响漏洞发现成本。
llmai_agent漏洞挖掘
RT @0xAsm0d3us: some alpha drop for doing inexpensive vuln research. instead of writing an article on the prompts/process behind this bounty (and more), I am dropping some prompts and the thought process I used as part of this research. ik you might say prompts don't matter much, frontier models' baseline intelligence can rawdog vuln discovery (and it is true to a good extent), but there is a high chance that you either do not have access to cyber models, or even if you do, they are expensive (and with heavy guardrails). The idea is, these prompts work well with open-weight/less expensive models. Not saying these will outperform the raw intelligence and capabilities of frontier models, but open-weight models perform much better with a bounded/goal-specific approach (where the goal is set, and the search space is massive) rather than open-ended exploration (where the goal is vague, and the search space is massive). anyway, here are some prompts. I don't need to share much, because you can just create variations of these and apply them wherever you wish. - find places where the app is supposed to enforce something, but doesn't actually enforce it. - find security rules that are enforced in one part of the app, but just assumed to be true in another. - find security assumptions the app relies on, but never actually checks or enforces. - find places where the app depends on undocumented behavior, and what happens if that behavior changes. - find operations that are secure on their own, but become vulnerable when you combine or chain them together. - find cases where the same object can be accessed in different ways, but each way ends up having different permissions. - find objects whose identity can be changed or rebound to another user, without going through the right checks. - find requests that get rejected or fail, but still end up changing something or triggering a side effect. - find security checks that only work if certain events happen in a specific order, and what happens if that order changes. - find operations where the transaction fails or rolls back, but some of the side effects still happen. - find things you can still do with an object even after it has been deleted, or access to it has been revoked. - find state changes that can be reversed or undone by someone who shouldn't have permission to do so. - find objects that can end up in two contradictory states at the same time, and what operations become possible because of that. I take such prompts, put it in a mutator (which has threat model of the project I am doing sec engagement), the mutator will mutate the prompts based on the threat model, and spawn swarm of agents, with different starting prompt and a bounded goal, the process repeats till all paths are exhauted, or some new signal is generated, which then feeds back to mutator. Doing this using a cheap model is very effective and sometimes it might yield you something even expensive models miss, we are just trying to maxximise the search space, from as many angles as possible, and once this process generates enough signals, just use a frontier model to confirm/triage issues, or for finding similar variants of such issues, that's basically it. There is v less moat is making a custom harness (unless you are an elite vuln research who can codify their approach in it or a 100x agentic engineer, I am neither).