Detects suspicious usage of the mode field in SendParameters struct instances.

Incorrect usage of the mode field in SendParameters can lead to unintended behavior when sending messages, such as incorrect flags being set, which can cause security vulnerabilities or unexpected contract behavior.

What it checks:

  • Ensures that the mode expression only uses the bitwise OR operator |.
  • Warns if integer literals are used instead of symbolic constants.
  • Warns if the same flag is used multiple times in the mode expression.
// Suspicious usage:
send(SendParameters{
    to: recipient,
    value: amount,
    mode: SendRemainingBalance | SendRemainingBalance // Bad: Duplicate flag
});

// Correct usage:
send(SendParameters{
    to: recipient,
    value: amount,
    mode: SendRemainingBalance | SendDestroyIfZero // Ok
});

Hierarchy (view full)

Constructors

Properties

severity: Severity = Severity.MEDIUM

Gets the severity of the detector.

Accessors

  • get id(): string
  • Gets the short identifier of the detector, used in analyzer warnings.

    Returns string

    The unique identifier of the detector.

  • get shareImportedWarnings(): WarningsBehavior
  • Defines the behavior of warnings generated by this detector when working with multiple projects within a single Tact configuration.

    Here are the available options:

    1. "union" Leave this value if you don't care about warnings generated in other projects.
    2. "intersect" If the warning is generated for some source location of the imported file, it should be generated by each of the projects. Example: Constants from an imported file should not be reported iff they are unused in all the projects, so you need "intersect".

    Returns WarningsBehavior

  • get usesSouffle(): boolean
  • Checks whether this detector needs the Soufflé binary to be executed.

    Returns boolean

Methods