VegaSec / Solidity scan report

access-control-simple-suicide.sol

VSS-20261003-JJKP2WIX · generated Oct 3, 2026, 7:54 PM

Watch3 findings1 critical1 highPasted sourcesemgrep 1.163.0

Verdict is derived from severity counts via the same deterministic formula every VegaSec report uses. access-control-simple-suicide.sol was scanned from pasted source. This is static-analysis triage, not a certification or formal audit attestation.

Signature

signed

This report is signed. Anyone can verify that these exact bytes came from us, with no account, no wallet and no API key. The signature proves integrity and authorship. It does not prove the audited contract is safe: read the coverage status and the limitations above.

sha256
1d9a9178e087cbc5...0ed2ffcc
Signed by
Ed25519 key vsig-2026-09
Canonical version
vss-canonical-1
Bytes served
stored canonical text, byte for byte

PDF artifact

Queued artifact pipeline · not blocking on the scan

Not requested

No PDF artifact has been requested for this report yet. The HTML report and the Markdown export already carry the full disclaimer and limitations inline. PDF synthesis is a queued artifact, not part of the scan path.

Status endpoint

GET /report/solidity/VSS-20261003-JJKP2WIX/export.pdf

Solidity evidence report

3 audit findings

critical: 1high: 1medium: 0low: 0informational: 1

Severity distribution

Executive summary

  • 3 findings surfaced (1 critical, 1 high, 0 medium, 0 low, 1 informational).
  • CRITICAL · selfdestruct call — exploitability unknown.
  • HIGH · SimpleSuicide.sudicideAnyone() (access-control-simple-suicide.sol#12-14) allows anyone to destruct the contract (sudicideAnyone) — exploitability high.
  • Automated static analysis only. A human operator review has not been attached to this report.
semgrep 1.163.0
  • criticalCentralizationConfidence: unknownExploitability: unknownDetector: semgrep

    selfdestruct call

    Affected location
    access-control-simple-suicide.sol:13
    Detector / source
    semgrep · semgrep:vegasec-selfdestruct

    Evidence

    selfdestruct call. Even with access control, selfdestruct introduces upgrade risk and historical state loss. Audit access control carefully or remove.

    Exploitability notes

    Analyzer did not report a confidence level; treat as unverified until reviewed.

    Remediation

    Document the trust boundary, set up time-locked multisig ownership, and surface admin-only functions in the deployment runbook.

    Limitations

    • Analyzer did not report confidence; fail closed and treat the finding as unverified.
    • Static analysis did not prove exploitability; do not present this as an exploit claim.
    • Analyzer output did not include a source excerpt for this finding.
  • highAccess controlConfidence: highExploitability: highDetector: slither

    SimpleSuicide.sudicideAnyone() (access-control-simple-suicide.sol#12-14) allows anyone to destruct the contract

    Affected location
    access-control-simple-suicide.sol:12-14 · sudicideAnyone
    Detector / source
    slither · slither:suicidal

    Evidence

    SimpleSuicide.sudicideAnyone() (access-control-simple-suicide.sol#12-14) allows anyone to destruct the contract

    Exploitability notes

    High-confidence detection of a severe pattern; treat as exploitable until disproven by manual review.

    Remediation

    Gate privileged functions behind a tested role/ownership pattern (e.g. OpenZeppelin Ownable/AccessControl). Avoid tx.origin for authorization.

    Limitations

    • High analyzer confidence, still requires source-level review before promotion.
    • Exploitability is inferred from a severe high-confidence static signal, not from a live exploit proof.
    • Analyzer output did not include a source excerpt for this finding.
  • informationalLogicConfidence: highExploitability: lowDetector: slither

    Version constraint ^0.4.0 contains known severe issues (https://solidity.readthedocs.io/en/latest/bugs.html)

    Affected location
    access-control-simple-suicide.sol:8 · ^0.4.0
    Detector / source
    slither · slither:solc-version

    Evidence

    Version constraint ^0.4.0 contains known severe issues (https://solidity.readthedocs.io/en/latest/bugs.html) - DirtyBytesArrayToStorage - KeccakCaching - EmptyByteArrayCopy - DynamicArrayCleanup - TupleAssignmentMultiStackSlotComponents - MemoryArrayCreationOverflow - privateCanBeOverridden - IncorrectEventSignatureInLibraries_0.4.x - ExpExponentCleanup - NestedArrayFunctionCallDecoder - ZeroFunctionSelector - DelegateCallReturnValue - ECRecoverMalformedInput - SkipEmptyStringLiteral - ConstantOptimizerSubtraction - IdentityPrecompileReturnIgnored - HighOrderByteCleanStorage - OptimizerStaleKnowledgeAboutSHA3 - LibrariesNotCallableFromPayableFunctions. It is used by: - ^0.4.0 (access-control-simple-suicide.sol#8)

    Exploitability notes

    Informational signal; not directly exploitable without additional context.

    Remediation

    Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.

    Limitations

    • High analyzer confidence, still requires source-level review before promotion.
    • Direct exploitability is not established; keep the signal as a remediation/checklist item.
    • Analyzer output did not include a source excerpt for this finding.

Limitations

  • VegaSec runs static analysis only. Findings can include false positives, miss patterns the configured detectors do not cover, and never replace manual auditor judgement.
  • Scan ran slither and semgrep against a single sandboxed copy of the source. Multi-file dependency analysis beyond what slither resolves automatically is out of scope.
  • This report is not a certification, audit attestation, or financial advice.

Exploit reasoning

Reference-grade reasoning tied to evidence

  • a09f64e539d15266d342742da0cdd8d4ea7513dec0418d541a98ff1f499fc837 · centralizationcritical

    Not determined

    Question: Is this finding exploitable in this specific contract?

    Reason: Analyzer confidence or exploitability is unknown; the narrative would overclaim without operator review.

  • 69eb6b7405159092b2daa327018c42016cb70a30fb833f163e8c8e863c2b938e · access-controlhigh
    Confidence: high

    Conditions for the exploit are met by the analyzer evidence; treat as likely until disproven by operator review.

    Preconditions

    • Sensitive function lacks an explicit caller restriction or relies on tx.origin
    • Caller controls the path that reaches the function

    Action

    Attacker calls the unprotected function from an attacker-controlled address, bypassing the intended restriction.

    Impact

    Unauthorized state mutation: ownership transfer, parameter changes, balance writes, or admin-only operations executed by a non-admin.

    False-positive caveats

    • The function may be intentionally callable by anyone (e.g. a public mint with a price guard).
    • Access control may live in a modifier the analyzer did not parse.

    Remediation checklist

    • Replace tx.origin checks with msg.sender against a role registry.
    • Add a `onlyRole(...)` or equivalent modifier from a vetted access control library.
    • Add unit tests that assert non-admin callers revert.

Audit pipeline

Audit cockpit

Honest stage-by-stage view of what VegaSec ran against this contract. Automated stages do not replace a human operator review.

Passed: 5Partial: 3Blocked: 1
  1. Audit intake

    Passed320ms replay7:54 PM

    Normalize the submitted contract target and confirm it can enter the Solidity audit lane.

    Next: Acquire verified source or scan the pasted Solidity source.

  2. Source acquisition

    Passed1.4s replay7:54 PM

    Resolve pasted source or verified explorer source without treating malformed input as demo data.

    Next: Validate the analyzer toolchain against the acquired source.

  3. Toolchain validation

    Passed2.3s replay7:54 PM

    Confirm the configured static analyzers can run and produce parseable output.

    Next: Run static analysis and capture raw detector evidence.

  4. Static analysis

    Passed3 findings8.8s replay7:54 PM

    Run static analyzers against the sandboxed source and collect raw detector evidence.

    Next: Normalize detector output into one deduped finding set.

  5. Finding normalization

    Passed3 findings1.1s replay7:54 PM

    Dedupe detectors, classify vulnerability classes and compute severity-weighted risk.

    Next: Review exploitability conservatively against confidence and limitations.

  6. Exploitability review

    Partial3 findings1.9s replay7:54 PM

    Frame automated findings with conservative exploitability and limitation notes.

    Next: Draft remediation notes from the normalized evidence.

    • Automated exploitability review is conservative and does not replace a manual exploitability assessment.
  7. Remediation draft

    Partial3 findings1.5s replay7:54 PM

    Prepare remediation-oriented evidence for the shareable report artifact.

    Next: Attach an operator review artifact before claiming human review.

    • Remediation notes are generated from detector evidence and require project-specific engineering review.
  8. Operator review

    Blocked0ms replay7:54 PM

    Record whether a human operator artifact exists before buyer escalation.

    Next: Attach a real operator review artifact before claiming human review.

    • No operator review artifact is attached to this automated scan.
    • Human operator review has not been attached to this automated scan yet.
  9. Finalization

    Partial3 findings620ms replay7:54 PM

    Publish the automated report artifact or explain why the scan failed closed.

    Next: Share the report with explicit limitations and review state.

    Artifact: Automated Solidity report · solidity-2f746d702f766567

    • Final report is an automated static-analysis artifact; no operator review artifact is attached.

Report badges

Verified source

Badges describe the evidence carried by this report artifact, not financial value or future pricing. Operator-reviewed is never granted automatically.

How to read this report

Score, confidence, ranking: four moving parts, no hand-tuning.

Generated Oct 3, 2026, 7:54 PM · Solidity · access-control-simple-suicide.sol

Score bands

  • 0-19

    AVOID-style triage

    Multiple high or critical findings, low source confidence, or unverified context. Public action should pause until a Private Review or a re-scan with better evidence.

  • 20-49

    High caution

    Notable findings or thin evidence. Worth a Private Review before relying on the artifact.

  • 50-69

    Watch · this report

    Mixed signals: some evidence, some gaps. Re-scan after material changes to the target.

  • 70-89

    Clear surface (automated)

    No critical or high findings via static analysis. Not a safety claim: human review is still recommended for diligence work.

  • 90-100

    Strong surface (automated)

    No critical or high findings, verified source, and high source confidence. Not a safety claim: human review is still recommended for diligence work.

Score
Deterministic 0-100 derived from severity counts. Same formula across every report. Lower means more risk.
Confidence
Separate axis. Measures how much VegaSec trusts the input data. Low confidence pushes the verdict toward UNKNOWN; the two are never collapsed into one number.
Ranking / percentile
Only meaningful within the eligible Trust Index set. Shown on /trust-index when the eligible pool is large enough. Today the public index is a controlled preview.

Private Review is separate

A paid Private Review does not raise the public score on this report. Public score reflects public-source evidence only. Private Review adds operator attestation and a confidential memo, never a score bump.

Export and share

  • · Shareable public URL: copy from the report actions panel.
  • · Markdown export: every export carries the report id, target, verdict, generated timestamp, and the public-data disclaimer.
  • · PDF export: not in this MVP. Tracked as a follow-up. The Markdown export contains the same content and prints cleanly to PDF from a browser today.

Source provenance

This report scanned a Solidity source provided directly by the submitter (paste). No on-chain address is associated.

Scanned source (366 chars)

/*
 * @source: https://github.com/SmartContractSecurity/SWC-registry/blob/master/test_cases/unprotected_critical_functions/simple_suicide.sol
 * @author: -
 * @vulnerable_at_lines: 12,13
 */

//added prgma version
pragma solidity ^0.4.0;

contract SimpleSuicide {
  // <yes> <report> ACCESS_CONTROL
  function sudicideAnyone() {
    selfdestruct(msg.sender);
  }

}

Public-data disclaimer

Solidity scans are triage based on slither + semgrep static analysis. Output is not a certification, audit attestation or financial advice. Findings can include false positives and may miss patterns the configured detectors do not cover.