exploiting-integer-overflow-vulnerabilities

exploiting-integer-overflow-vulnerabilities is a skill for Claude Code, Codex from xalgorix/xalgorix. It costs 69 tokens per session (2,441 once invoked), scanned A, original, Apache-2.0.

A security testing method for finding integer arithmetic bugs in native programs such as C, C++, Rust, or Go. These bugs occur when numbers wrap, become too small, or change meaning before they control memory sizes, copies, indexes, or offsets.

In plain words
What is it for?
Use it during authorized security assessments to investigate integer overflow, underflow, truncation, signedness confusion, allocation errors, bounds-check bypasses, and related buffer overflows.
Why use it?
It helps connect a numeric error to a real memory-safety problem instead of treating the arithmetic bug alone as the impact.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/xalgorix/xalgorix/exploiting-integer-overflow-vulnerabilities
Any agent
npx skills add xalgorix/xalgorix --skill exploiting-integer-overflow-vulnerabilities
Clone the repo
git clone --depth 1 https://github.com/xalgorix/xalgorix

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for exploiting-integer-overflow-vulnerabilities

README.md
[![agentmods](https://agentmods.dev/badge/skills/xalgorix/xalgorix/exploiting-integer-overflow-vulnerabilities.svg)](https://agentmods.dev/skills/xalgorix/xalgorix/exploiting-integer-overflow-vulnerabilities)
Your own site
<a href="https://agentmods.dev/skills/xalgorix/xalgorix/exploiting-integer-overflow-vulnerabilities"><img src="https://agentmods.dev/badge/skills/xalgorix/xalgorix/exploiting-integer-overflow-vulnerabilities.svg" alt="Measured on agentmods" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,441 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00069 $0.02441
Opus 5 $0.00034 $0.01221
Sonnet 5 $0.00014 $0.00488
Haiku 4.5 $0.00007 $0.00244

Measured 5d ago against content hash 6daed78a792a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

exploiting-integer-overflow-vulnerabilities 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 5d 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.

internal/tools/skills/data/binary-exploitation/exploiting-integer-overflow-vulnerabilities/SKILL.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Exploiting Integer Overflow Vulnerabilities

When to Use

  • During authorized assessments of native code (C/C++/Rust/Go) where attacker-controlled integers feed size, length, count, index, or offset calculations.
  • When an allocation size is computed from arithmetic (count * elem_size, len - header, size + padding) that can wrap, producing an undersized buffer later written with the logical (un-wrapped) size — a classic integer-overflow-to-heap-overflow chain.
  • When a length/bounds check uses a narrow type (e.g. 1-byte size field) that can be overflowed to bypass validation while the real copy uses a larger value.
  • When signed/unsigned confusion causes a negative input to be treated as a huge positive size.

Critical: Concepts/Steps Most Often Missed

  • The overflow itself is rarely the impact — find the dangerous downstream use. An int wrap is only exploitable when the wrapped value sizes an allocation/copy/index. Always trace the tainted integer to a malloc, memcpy, read, loop bound, or array index.
  • Truncation across type widths. uint32_t product = (uint32_t)(count * elem_size) can wrap to a tiny value while a separate size_t to_copy = count * elem_size keeps the full value — allocation is small, copy is huge. Watch every cast to a narrower type.
  • Underflow on subtraction is just as dangerous. size_t payload = total_len - HEADER with total_len < HEADER underflows to a near-SIZE_MAX value, turning a "shrink" into an unbounded copy.
  • Signedness. A signed int read with scanf("%d") then cast to unsigned makes negatives become large positives, defeating if (x > LIMIT) checks.
  • Alignment/rounding re-introduces overflow after an initial guard. Custom allocators that pass an initial wrap check then do total += (8 - total) % total can wrap again for values near SIZE_MAX, yielding a tiny chunk (e.g. CVE-2025-54957).
  • Go/Rust wrap silently in release/normal builds. Go has no overflow panic by default; instrument with go-panikint; Rust wraps in release unless overflowing_*/checked arithmetic is used.

Read the full file on GitHub · 180 lines

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.

  1. 5d ago First seen · 180 lines · 69 tokens per session scan A 6daed78a792a

Subscribe to this mod's changes

exploiting-integer-overflow-vulnerabilities is a skill published in the GitHub repository xalgorix/xalgorix (955 stars, last pushed today), licensed Apache-2.0. It adds 69 tokens to every session and 2,441 once invoked, about $0.0003 per session on Opus 5. 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.

Related

Other skills, from other repositories

bugbountyrules

Use for ANY bug bounty, penetration test, or web/API/mobile security assessment: recon, testing endpoints, analyzing Burp traffic or any bug-bounty platform's MCP (HackerOne, Intigriti, Bugcrowd, YesWeHack, Immunefi), reviewing APKs, bypassing a WAF, enforcing scope, hunting a specific vuln class, validating findings…

sanjarbiy/bugbountyrules · 220 tokens

hunt-ato

Hunt account takeover taxonomy — 9 distinct paths to ATO, plus chains. Paths: (1) password reset flaws (host-header injection redirects token, predictable/numeric token, Referer leak, no-expiry/reuse), (2) email change without re-auth, (3) OAuth account-link CSRF, (4) MFA bypass (per hunt-mfa-bypass), (5) session…

Zyrexnn/Cybermes · 241 tokens

evidence-hygiene

Evidence-capture and PoC-redaction discipline for bug-bounty submissions: cookie redaction protocol (which fields to mask, Preview annotation / Burp panel hiding / DevTools workflow), PII black-bar discipline (what to mask in other-user data — names, emails, phones, faces — vs what is safe to leave — usernames, trace…

Zyrexnn/Cybermes · 190 tokens

hunt-api-misconfig

Hunt API security misconfiguration — mass assignment, prototype pollution, HTTP verb tampering. Mass assignment: send {isadmin:true, role:admin, verified:true} on profile/account/reset endpoints — server blindly applies. JWT signature/crypto forging (alg:none, key confusion, kid/jku) is owned by hunt-jwt-crypto; this…

Zyrexnn/Cybermes · 207 tokens

apk-redteam-pipeline

End-to-end Android APK red-team pipeline — automated APK acquisition (Play Store + apkpure + apkmirror fallback), jadx decompilation, secret/URL/JWT/Firebase grep, pinned-cert extraction, exported-component enumeration, Frida runtime instrumentation templates, intent-injection probes. Built from an authorized external…

Zyrexnn/Cybermes · 145 tokens

bugcrowd-reporting

Bugcrowd-specific reporting tactics complementing report-writing: VRT category search-and-fallback strategy when no exact match exists, manual severity override when VRT defaults underrate impact, severity-request paragraph as first body section, OOS-clause rebuttal templates (rate limiting on auth-flow endpoints…

Zyrexnn/Cybermes · 171 tokens