prompt listlengths 2 2 | source stringclasses 3
values | severity stringclasses 5
values | category stringclasses 186
values | has_code bool 2
classes | has_poc bool 2
classes | reference_response stringlengths 23 5k | firm stringclasses 26
values | quality_score float64 0 5 | protocol stringclasses 398
values |
|---|---|---|---|---|---|---|---|---|---|
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | high | other | false | false | ## High: No check `_amt` value under withdraw
### Description
At the lines:
- https://github.com/orbxball/stablecoins-ypool/blob/5d80af7aeeff9f9b8f6d47d0334d36db3e97e5e4/contracts/StrategyDAIypool.sol#L207
- https://github.com/orbxball/stablecoins-ypool/blob/5d80af7aeeff9f9b8f6d47d0334d36db3e97e5e4/contracts/StrategyT... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | access-control | false | false | ## Low: Design choices and security considerations for VestingWallet
### Description
Below are some design choices and security considerations for the vesting wallet:
1. **Adding tokens during the vesting period** has the same effect as if they were added before the start of the period. As a result, a percentage of t... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | other | false | false | ## Low: [06] `execute()` accepts stray ETH and leaves it stuck in the router
### Description
### Vulnerability details
`TrailsRouter.execute` is payable but does nothing with `msg.value`. When called standalone, any attached ETH remains on the router, where it can later be swept by whoever controls subsequent router ... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | high | initialization | false | false | ## High: The auction account may be closed before the NFT is transferred to the winner
### Description
**Description**
If the user does not pay fees with a single transaction, but, for example, pays a fee via a separate transaction and calls the finalize method separately, all lamports from the auction account will b... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | high | other | false | false | ## High: | Overwriting Previous Name
### Description
**Description**
When a bid is accepted through `acceptBidForName` or an offered name is purchased through `buyName`, there is no check that the NFT the name shall be transferred to is already named. As a result, a user may unexpectedly lose their old name upon tran... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | initialization | false | false | ## Low: flashFeeFactor is uninitialized at declaration leading to zero-fee flash loans enabled by default
### Description
## Handle
0xRajeev
## Vulnerability details
## Impact
flashFeeFactor is uninitialized at declaration and so zero initially until set by setFlashFeeFactor(). As indicated in one of the the expl... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | initialization | false | false | ## Low: Redundant checks
### Description
While requirements are indispensable for ensuring the proper usage and security of contracts, an instance of redundant validation has been identified.
In this scenario, the code validates that the spender possesses sufficient allowance before transferring the specified amount.... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | initialization | true | false | ## Low: Insu�ficient enforcement of immutability of system logic variables through the Solidity compiler
### Description
The system logic of the Liquity Protocol is supposed to be immutable after deployment. For this reason, variables are marked immutable so they can only be assigned once in the constructor:
```solidi... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | oracle | true | false | ## Low: Issues when handling tokens in `fulfillSwap()` function
### Description
## Vulnerability Details
In `StabilityBranch#fulfillSwap()`function, it use Chainlink's Data Stream to verify price:
From scope, these tokens are supported:
But there are 2 problems at here:
* SUSDE and WEETH token do not exist in da... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | overflow | true | false | ## Low: Market source removal is dangerous
### Description
The `removeSourceAtIndex` private function makes a number of assumptions about the state of the contract. If it is ever called when any of these assumptions are invalid, then there will be serious security implications.
```solidity
/**
* @param index Index o... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | reentrancy | true | false | ## Medium: Reentrancy in executeTransaction() Won't Fix
### Description
In `MixinTransactions`, `executeTransaction()` and `batchExecuteTransactions()` do not have the `nonReentrant` modifier. Because of that, it is possible to execute nested transactions or call these functions during other reentrancy attacks on the... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | gas | other | true | false | ## Gas: Redundant on-chain data
### Description
`StakingPoints.stakes` is a mapping which keeps track of user balances and the block timestamp of their last update:
```solidity
struct Stake {
// balance at last update to stake
uint224 balance;
// timestamp of last update to stake
uint32 blockTimestamp;
}
///... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | dos | true | false | ## Low: [2] Unbounded loops may run out of gas
### Description
The call to `ecrecover()` costs 3000 gas per call, and if there are too many validators, the update of the validator set may pass, but large batches will fail | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | front-running | true | false | ## Medium: Magnetar unwrap operations broken due to bad ownership and checks
### Description
The `_processWrapOperation` function can be triggered on the Magnetar contract to wrap/unwrap the user's tokens into or out of the TOFT contracts. This function allows 2 selectors, `wrap` and `unwrap` to be called.
The issue ... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | rounding | true | false | ## Low: Rebase Limiter isLimitReached will almost always return false due to rounding error
### Description
**Severity:** Low
**Path:** PositiveTokenRebaseLimiter.sol:isLimitReached#L103-L115
**Description:**
The function `isLimitReached` is used in `getSharesToBurnLimit` to provide an early return if the rebase li... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | high | liquidation | true | false | ## High: Incorrect Protection Period Checks May Deny Valid Claims
### Description
The `canClaimProtection` function from `UserBase` contract is designed to determine whether a user can claim protection under a specific Blueprint. This function evaluates the eligibility based on several parameters, including the end ti... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | logic | true | false | ## Medium: Contract Owner Cannot Recover Dead Heroes Due to Conflicting State Validation Logic
### Description
The `Dragma` contract contains a critical logic error in the `unstakeDiedHeroes()` function that creates an impossible execution condition, preventing the contract owner from recovering dead heroes. The vulne... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | cyfrin_structured | low | token | false | false | ## Low: Dust amounts of swapped collateral tokens remain in `SmartVaultYieldManager`
### Description
Due to rounding, swaps made via Uniswap-style routers with exact input parameters can result in residual dust amounts left in the calling contract. This is not an issue for deposits to Gamma Vaults, as all swapped toke... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | high | dos | false | false | ## High: Unbounded loop in `_removeNft` could lead to a griefing/DOS attack
### Description
_Submitted by shw, also found by cmichel, gpersoon, pauliax, Sherlock, and toastedsteaksandwhich_
Griefing/DOS attack is possible when a malicious NFT contract sends many NFTs to the vault, which could cause excessive gas cons... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | access-control | false | false | ## Low: Front running attacks by the `onlyOwner`
### Description
`verifyingSigner` value is not a constant value and can be changed with `setSigner` function, before a function using `verifyingSigner` state variable value in the project, `setSigner` function can be triggered by `onlyOwner` and operations can be blocke... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | high | token | true | false | ## High: Reversion in `ApiologyDAOToken` transfer due to insufficient governance tokens
### Description
The `ApiologyDAOToken` contract allows for the dynamic adjustment of the number of governance tokens associated with each NFT through the `ApiologyDAOToken::changeGovTokensPerNFT` function.
```solidity
File: Apiolo... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | oracle | false | false | ## Medium: Lack of slippage and deadline during withdraw and deposit
### Description
When users call `withdraw()` to burn their `ezETH` and receive redemption amount in return, there is no provision to provide any slippage & deadline params. This is necessary because the `withdraw()` function [uses values from the ora... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | cross-chain | false | false | ## Medium: Excess Gas Remains in SpokePool
### Description
The `Polygon_SpokePool` contract is intended to support sending USDT0 to Ethereum mainnet. This is done when an account calls the [`executeRelayerRefundLeaf` function](https://github.com/across-protocol/contracts/blob/d9826e30b51bbb3067df07c9532f4a5f6fe56f1c/c... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | cross-chain | true | false | ## Low: Not validating `MIN_APPLICATION_PERIOD` can lead to stolen funds
### Description
`MIN_APPLICATION_PERIOD` is defined on the `Frankencoin` constructor and is immutable. In case the contracts are deployed with `_minApplicationPeriod = 0`, an attacker can become a minter, burn the token and steal assets on other ... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | other | false | false | ## Low: Some view functions do not consider accrued interest
### Description
`LendingAssetVault`'s `previewWithdraw`, `previewRedeem`, `maxWithdraw`, `maxRedeem`, `previewDeposit`, and `previewMint` are used to calculate the assets or shares required for withdrawal/redeem or mint/deposit operations. However, these fun... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | initialization | true | false | ## Low: Missing Validation for Normal Ball Max Range Causes Critical Function Failures Due to Combination Library Limits and Underflow
### Description
The `normalBallMax` parameter can be set to values that break critical functions. The [`Combinations::choose`](https://github.com/code-423n4/2025-11-megapot/blob/5cda57... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | oracle | true | false | ## Low: NatSpec is incomplete
### Description
1. File: src/Funding.sol (lines [95-112](https://github.com/code-423n4/2022-04-badger-citadel/blob/dab143a990a9c355578fbb15cd3c884614e33f42/src/Funding.sol#L95-L112))
Missing: `@param _citadelPriceInAssetOracle`
2. File: src/KnightingRound.sol (lines [98-119](https://... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | oracle | true | false | ## Medium: Single hardcoded cap used for multiple tokens in a pump causing some assets to be more stale, while having no effects on other stable assets
### Description
### Impact
When multiple tokens are handled in MultiFlowPump.sol, during trading, the pump might either unfairly reflects volatile assets to be more s... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | initialization | true | false | ## Low: Unused approval from Treasury to TokenLock
### Description
In the constructor of Treasury we have this line:
```
_token.approve(address(_locker), type(uint256).max);
```
- https://github.com/prisma-fi/prisma-contracts/blob/c0122d27677cd4e1aaee7f1e21f807ccadf46ac8/contracts/dao/Treasury.sol#L111
But TokenLocke... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | high | cross-chain | true | false | ## High: Incorrectly reading the offset from the received data parameter to get the `depositNonce` in the `BranchBridgeAgent::anyFallback()` function
### Description
Not reading the correct offset where the `depositNonce` is located can lead to setting the status of the wrong deposit to "Failed" when the [`_clearDepos... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | liquidation | false | false | ## Medium: Avoidable misconfiguration could lead to `INVEscrow` contract not minting `xINV` tokens
### Description
[Market.sol#L281-L283](https://github.com/code-423n4/2022-10-inverse/blob/main/src/Market.sol#L281-L283)
If a user creates a market with the **INVEscrow** implementation as **escrowImplementation** and f... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | high | dos | true | false | ## High: `EtherFiLib::_initiateWithdrawImpl` will revert because rebase tokens transfer 1-2 less wei
### Description
`EtherFiLib::_initiateWithdrawImpl` will revert because rebase tokens transfer 1-2 less wei
### Impact
Contract functionality DoS
### Recommendation
```diff
function _initiateWithdrawImpl(uint256 weET... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | overflow | true | false | ## Low: Missing checks on new Boost Cap
### Description
1. setBoostCapForVault function at TurboBooster.sol#L59 is missing checks to see if newBoostCap>getBoostCapForVault\[vault]
2. This is required since vault might already be at old boost cap.
3. Setting lower boost cap would mean that boosting is already over... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | gas | storage | true | false | ## Gas: ++i costs less gas compared to i++ or i += 1 in for loops (\~5 gas per iteration)
### Description
\++i costs less gas compared to i++ or i += 1 for unsigned integer, as pre-increment is cheaper (about 5 gas per iteration). This statement is true even with the optimizer enabled.
i++ increments i and returns th... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | dos | false | false | ## Medium: GMXVault can stop working in case if GMX will change `Keys.MAX_CALLBACK_GAS_LIMIT` to smaller than 2 millions
### Description
Keys.MAX_CALLBACK_GAS_LIMIT is configurable param inside GMX protocol, which can be changed to value that is smaller than 2 millions. As Steadefi doesn't callback gas limit is hardco... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | high | dos | true | false | ## High: getLockedCount is iterating over all history of delegations ✓ Addressed
### Description
`getLockedCount` is iterating over all delegations of a specific holder and may even change the state of these delegations by calling `getState`.
**code/contracts/delegation/TokenState.sol:L60-L71**
```
function getLoc... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | overflow | false | false | ## Low: SafeMath and SafeCast Usage
### Description
The contract does not utilize Solmate's FixedPointMathLib or OpenZeppelin's SafeCast libraries for arithmetic operations, which could streamline the readability of the code.
### Recommendation
We recommend using FixedPointMathLib and SafeCast libraries to handle ari... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | other | true | false | ## Medium: Reversed order of parameters in allowance function call ✓ Fixed
### Description
When trying to pull the maximum amount of tokens from an approver to the allowed spender, the parameters that are used for the `allowance` function call are not in the same order that is used later in the call to `safeTransferFr... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | other | true | false | ## Low: Discrepancy between code and comments ✓ Addressed
### Description
There is a discrepancy between the code at:
**code/contracts/masset/BasketManager.sol:L417**
```
require(weightSum >= 1e18 && weightSum = 100 && <= 400%");
```
And the comment at:
**code/contracts/masset/BasketManager.sol:L409**
```
\* ... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | high | other | true | false | ## High: Stakers Can Lose Their Earned `aSugar`
### Description
Users who stake a second time without calling `fullyClaimReward()` will lose their accumulated unclaimed `aSugar`. Furthermore, the second stake could be executed by somebody else via `deligateStake()` if there is an active allowance.
Example:
The user ... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | gas | other | false | false | ## Gas: `storage` pointer to a structure is cheaper than copying each value of the structure into `memory`, same for `array` and `mapping` (1 instance)
### Description
* Deployment. Gas Saved: **8 208**
* Minumal Method Call. Gas Saved: **106**
* Average Method Call. Gas Saved: **-970**
* Maximum Method Call. G... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | other | false | false | ## Low: Use enumerableSet
### Description
**Description**
There is an efficient Library which to search/find/delete for O(1) time
https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/utils/structs
/EnumerableSet.sol
Use it here, instead of iterating over arrays.
contracts/Actuary.sol:10
contra... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | front-running | true | false | ## Medium: Burning an NFT can be used to block voting
### Description
A new validation in the `accept()` function has been introduced in order to mitigate a potential attack to the party governance.
By burning an NFT, a party member can reduce the total voting power of the party just before creating a proposal and vo... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | front-running | false | false | ## Medium: Centralization risks
### Description
`receiver` can front-run escrow creation and change fees: https://github.com/MetaLex-Tech/LeXscrow/blob/94ca277528bb25b8421dc127941c18915144eb29/src/DoubleTokenLexscrowFactory.sol#L192-L204, https://github.com/MetaLex-Tech/LeXscrow/blob/94ca277528bb25b8421dc127941c189151... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | oracle | true | false | ## Medium: Risk of Backing Value Loss for Non-Whitelisted Token Holders Acknowledged
### Description
The `withdraw` function restricts withdrawals to whitelisted addresses via `_requireWhitelisted(msg.sender)`, ensuring that only tokens held by whitelisted users can be redeemed for their backing value. However, if to... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | storage | false | false | ## Low: Redundant status variable in `HanjiTrieFactory`
### Description
The issue has been identified within the [HanjiLOBFactory](https://github.com/longgammalabs/hanji-contracts/blob/70b15ec4d9e7578248141604503843716a67d875/src/HanjiLOBFactory.sol#L101) and [HanjiTrieFactory](https://github.com/longgammalabs/hanji-c... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | liquidation | true | false | ## Medium: Task Functionality completely sidestepped via `autoWithdraw`
### Description
_Submitted by GalloDaSballo_
[Project.sol#L770](https://github.com/code-423n4/2022-08-rigor/blob/5ab7ea84a1516cb726421ef690af5bc41029f88f/contracts/Project.sol#L770)
`autoWithdraw` will send funds to the `builder`, we can use thi... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | other | false | false | ## Low: Add zero address checks
### Description
It is standard practice to check incoming addresses are not zero. Consider adding such a check
in `setAutoTrader()`.
**Team response:**
"added zero address check to setAutoTrader."
**Mitigation review:**
Change applied correctly. | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | token | true | false | ## Medium: `CEthInterface#mint()` reading non-existing returns makes `topUp()` with native token always revert
### Description
_Submitted by WatchPug_
[CTokenInterfaces.sol#L345](https://github.com/code-423n4/2022-04-backd/blob/c856714a50437cb33240a5964b63687c9876275b/backd/interfaces/vendor/CTokenInterfaces.sol#L345... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | overflow | true | false | ## Low: Integer Overflow
### Description
## receive_balance Function Overview
`receive_balance` reads the existing balance of a given address, adds the provided amount to it, and then writes the updated balance back to the storage.
## Potential Issue
There is a potential integer overflow in the addition operation `... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | gas | other | true | false | ## Gas: [11] `keccak256()` should only need to be called on a specific string literal once
### Description
It should be saved to an immutable variable, and the variable used instead. If the hash is being used as a part of a function selector, the cast to `bytes4` should also only be done once
*There is 1 instance of ... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | dos | true | false | ## Medium: Denial Of Service Due To Excessive Gas Consumption
### Description
## Vulnerability Overview
The vulnerability lies in the potential for a malicious actor to exploit the `max_computation_budget` limit by flooding the order book with a large number of small orders. Each time an order is fully filled, the `p... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | cyfrin_structured | low | other | true | false | ## Low: <a name="GAS-3"></a>[GAS-3] `array[index] += amount` is cheaper than `array[index] = array[index] + amount` (or related variants) | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | gas | other | true | false | ## Gas: `ForgottenRunesWarriorsMinter`: `bidSummon()`and `publicSummon()`: Unnecessary require statement
### Description
The code is as such:
Logically speaking, `numSold + numWarriors 0 && numWarriors 0`, we don't need to check if `numSold < maxForSale` as it just can't happen.
I suggest removing the 2 `require(... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | other | false | false | ## Low: Confusing use of uint184 and uint196 types for pending values
### Description
The MetaMorpho contract uses the PendingLib library to update pending values of guardians, supply caps, and timelocks. The supply caps and pending timelock values, respectively stored in the `pendingCap` and `pendingTimelock` state v... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | oracle | false | false | ## Medium: TWAP can be manipulated
### Description
The contract uses the TWAP oracle to calculate the price for deposits and swaps performed through the pump mechanism. The observation window is set to 18.15 minutes.
However, two issues cause the TWAP to be easily manipulated:
1. Uniswap V3 pools are initialized wit... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | high | other | true | false | ## High: User’s funds are locked and lost when decreasing a position
### Description
**Severity**: Critical
**Status**: Resolved
**Description**
When a user decreases a position calling `decreasePosition()` within the `TradeFacet.sol` smart contract, a call to `lockForAnOrder` is executed. `lockForAnOrder` is lock... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | gas | signature | false | false | ## Gas: Unnecessary require in `SignatureValidator.recoverAddrImpl()`
### Description
`address signer = address(wallet);` so `require(signer != address(0), 'SV_ZERO_SIG');` is redundant in `SignatureValidator.recoverAddrImpl()`, as it would already have reverted in `wallet.isValidSignature(hash, sig)`, because of a fu... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | dos | true | false | ## Medium: Various vault accounting inconsistencies and potential unhandled reverts
### Description
**Description:** `BunniHub::hookHandleSwap` overestimates the reserves deposited to ERC-4626 vaults and assumes that within the call to `_updateVaultReserveViaClaimTokens()` it deposits enough to execute the swap:
In ... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | dos | false | false | ## Medium: Absence of Rate Limiting on Critical Endpoints(All servers URLs)
### Description
**Severity**: Medium
**Status** : Acknowledged
**Description**:
Several endpoints in the Hinkal Protocol, particularly those involved in sensitive operations such as the https://polygon.server.hinkal.pro/users/0xC6Cd9d90F13... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | token | false | false | ## Medium: Vault is Not Compatible with Fee Tokens and Vaults with Such Tokens Could Be Exploited
### Description
_Submitted by 0x1337, also found by 0x52, 0xDjango, 0xsanson, berndartmueller, BondiPestControl, BowTiedWardens, cccz, dipp, GimelSec, hake, hickuphh3, horsefacts, hubble, IllIllI, MaratCerby, MiloTruck, m... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | gas | other | true | false | ## Gas: Delete `TroveManager::_removeStake` and perform this as part of `_closeTrove` since they always occur together
### Description
**Description:** `TroveManager::_removeStake` is only ever called immediately before `_closeTrove` so the function can be deleted and its functionality implemented more efficiently in... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | access-control | false | false | ## Low: Inability for users to permissionlessly stake and earn yield
### Description
**Description:** The intention of the protocol as specified in the kick-off call and in discussion with the client is that users should be able to permissionlessly:
* buy hBTC from a decentralized exchange
* stake/unstake hBTC in a pe... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | high | initialization | true | true | ## High: Users can gain free tokens through the BunniSwap swap functionality
### Description
During token swaps, users can receive a nonzero amount of output tokens even when they provide zero input tokens, allowing them to acquire free tokens without contributing any input tokens for the swap.
The `computeSwap` func... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | other | false | false | ## Low: NON-LIBRARY/INTERFACE FILES SHOULD USE FIXED COMPILER VERSIONS, NOT FLOATING ONES
### Description
Avoid floating pragmas for non-library contracts.
While floating pragmas makes sense for libraries to allow them to be included with multiple different versions of applications, it may be a security risk for appl... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | other | false | false | ## Medium: Incorrect Accounting in forceWithdraw Leading to Liquidity Miscalculation
### Description
The `forceWithdraw` function does not correctly update `tokenTotalOnLine` or `totalOnLine` after executing a forced withdrawal. This leads to inaccurate tracking of funds, as the withdrawn amount remains counted as par... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | cyfrin_structured | low | access-control | true | false | ## Low: Follow function declaration solidity style guide in `BaseContract`
### Description
Functions `pause` and `unpause` defines the visibility `public` after the modifier `onlyOwner`. As per the [Solidity Style Guide](https://docs.soliditylang.org/en/latest/style-guide.html#function-declaration), the order expects ... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | oracle | false | false | ## Medium: Minimum Price Deviation Is Calculated Incorrectly in Price Oracles
### Description
The [`getPrice()` function of `ETHPriceOracle`](https://github.com/AladdinDAO/fx-protocol-contracts/blob/56a47eab8d10334e479df83a2b13a8b68ce390e9/contracts/price-oracle/ETHPriceOracle.sol#L61-L74), [the `getPrice()` function ... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | other | true | false | ## Low: Invalid bundles can be created
### Description
It seems that even if `tokenIds.length` is 0, a bundle token will still be created. Currently, there does not seem to be any advantage, but a check for `tokenIds.length > 0` will prevent such invalid bundles.
Note: Borrowing on such a bundle will fail currently ... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | dos | false | false | ## Low: Iterating allProducts array can cause the gas limit to exceed
### Description
**Severity**: Low
**Status**: Unresolved
**Description**
The variable allProducts maintains an array of created products. If an external smart contract attempts to iterate over the array to validate if an address is a valid produc... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | dos | false | false | ## Low: `totalRewards` miscalculation during reward redistribution.
### Description
**Description**
TokensFarm.sol: function withdraw(), line 1425.
TokensFarmSDK.sol: function_payoutRewardsAndUpdateState(), line 1246.
Perpetual TokensFarm.sol: function withdraw(), line 1437.
PerpetualTokensFarmSDK.sol: function_payou... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | solodit_api | medium | Business Logic | false | false | Source: https://github.com/sherlock-audit/2022-11-frankendao-judging/issues/31
## Found by
0x52
## Summary
Staking#changeStakeTime and changeStakeAmount allow the locking bonus to be modified. Any change to this value will cause voting imbalance in the system. If changes result in a higher total bonus then existin... | Sherlock | 4 | FrankenDAO |
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | token | true | false | ## Low: No Check if onERC721Received Is Implemented
### Description
The `PuttyV2.fillOrder` will mint a long position NFT and short position NFT to the order maker and taker. When minting a NFT, the function does not check if a receiving contract implements onERC721Received().
The intention behind this function is to... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | cyfrin_structured | low | input-validation | true | true | ## Low: Transferring all the investor balance from a non-us investor to a new us investor allows to bypass the `usInvestorLimit`
### Description
`ComplianceServiceLibrary.completeTransferCheck()` runs a list of validations to prevent investor limits (regional and global) from being bypassed in case the recipient of th... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | cross-chain | true | false | ## Medium: Incorrect address provided as the receiver when bridging and minting the Node Key token on the L2
### Description
**Severity**
**Impact:** Medium, The user may not expect the `msg.sender` to receive the token on L2 instead of the `_to` address provided.
**Likelihood:** Medium, as this will happen all the ... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | other | false | false | ## Medium: OlympusGovernance - active proposal does not expire
### Description
_Submitted by reassor_
Contract `OlympusGovernance` allows controlling protocol through on-chain governing. The issue is that once proposal is active it does not expire, which means that until the new proposal will be selected, anyone can ... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | overflow | false | false | ## Medium: Using deprecated libraries
### Description
**Description**
Сontract “GOVToken” uses SafeMath library to prevent overflow after arithmetical operations.
Solidity from has reverted on overflow by default, the only reason to use SafeMath is to
send custom messages on reverts.
v0.8.0
**Recommendation**:
Rem... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | token | true | false | ## Medium: TRST-M-1 Unsafe transferFrom breaks compatibility with 100s of ERC20 tokens
### Description
**Description:**
In Ninja vaults, the delegated strategy sends profit tokens to the vault using
`depositProfitTokenForUsers()`. The vault transfers the tokens in using:
The issue is that the code doesn't use the `s... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | oracle | false | false | ## Low: Investors can lose funds due to delay in withdrawal
### Description
**Severity**: Low
**Status**: Acknowledged
**Description**
In contract FEYTraderJoeProduct, the rescueTokens() function allows an admin to withdraw all the tokens from the contract after 3 weeks from the tranche end time. Ideally, the inves... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | liquidation | true | false | ## Low: `updateLiquidationContract()` might lock collaterals and funds in the current liquidator contract
### Description
In `LiquidationHandler::updateLiquidationContract()`, the loan liquidator contract can be updated.
`src/lib/LiquidationHandler.sol# L74`
There are two vulnerable conditions: `updateLiquidationCo... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | gas | other | false | false | ## Gas: Set the number of optimizer runs individually
### Description
Some development environments allow the number of optimizer runs to be defined individually for each contract. This is difficult to achieve in foundry. But hardhat is the best example. The main limitation to the number of runs in the case of contrac... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | other | false | false | ## Low: closePositionRequest value not updated on request fulfillment
### Description
**Severity**: Informational
**Status**: Resolved
**Description**
SakeVaultV2.sol - In fulfilledRequestSwap(), we have the mapping closePositionRequest is not updated for the user. The mapping is expected to be true in order here:
... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | other | true | false | ## Low: BalancerLBPSwapper - tokenSpent and tokenReceived should be immutable
### Description
Acc. to the inline comment both `tokenSpent` and `tokenReceived` should be immutable but they are not declared as such.
### Recommendation
Declare both variable `immutable`. | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | other | true | false | ## Low: Omissions in Events
### Description
Throughout the codebase, events are generally emitted when sensitive changes are made to the contracts.
However, some events are missing important parameters.
The events should include the new value and old value where possible: | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | rounding | true | false | ## Medium: `Looping.openPosition()` insufficient division factor
### Description
In `Looping.openPosition()` function, when users provide the expected flashloan premium payment in the `yieldAsset`, it is swapped into `debtAsset`, where the `minAmountOut` expected from the swap is calculated as follows:
```solidity
fu... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | storage | false | false | ## Low: Non-optimistic builder builds optimistically
### Description
After finalizing a block, Beacon-Kit has the following check when sending the new `engine_fork-choiceUpdatedV3` to the EL client:
```go
if !s.shouldBuildOptimisticPayloads() && s.localBuilder.Enabled() {
s.sendNextFCUWithAttributes(ctx, st, blk, l... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | medium | other | false | false | ## Medium: Dead bribe vaults can be used to prevent poking VotingEscrow positions
### Description
In order to vote in Voter, users are first required to create a position in **VotingEscrow**, locking their governance tokens for a desired lock duration. During this time, the effective voting power of their position (`b... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | rounding | false | false | ## Low: Unsafe Data Type Casting
### Description
The issue has been discovered in the `getRedeemPrice` function of the `UsrRedemptionExtension` contract. When the `priceDecimals` equals to `USR_DECIMALS`, [the casting operation](https://github.com/resolv-im/resolv-contracts/blob/f4a09fa74498b19708b056af6adc070e1272b59... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | signature | false | false | ## Low: secp256r1 precompile does not check for signature malleability
### Description
The implementation of the `ecdsa.Verify` function from the `secp256r1` package is vulnerable to signature malleability attacks. This issue arises from the fact that the function accepts malleable signatures as valid inputs:
```go
/... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | solodit_api | high | Approve | true | false | _Submitted by cmichel, also found by WatchPug, jonah1005, gzeon, and TomFrench_
The `approve` function has not been overridden and therefore uses the internal *shares*, whereas `transfer(From)` uses the rebalanced amount.
#### Impact
The approved spender may spend more tokens than desired. In fact, the approved amount... | Code4rena | 3 | BadgerDAO |
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | high | other | false | false | ## High: Attackers will steal rewards from legitimate pools by making duplicate pools for listed token.
### Description
The per-token reward accrual without pool validation will cause reward theft for legitimate pools as attackers will create malicious pools and trigger reward distribution.
### Impact
Legitimate pool... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | other | false | false | ## Low: Conflicting flow of pending `upgradeFactory` and `setFactory`
### Description
Calling [`finalizeUpgrade`](https://github.com/EnsoFinance/shortcuts-contracts/blob/4902e55608f975f73772310955444110b1cfc4fc/contracts/EnsoBeacon.sol#L74) after `setFactory` can cause unexpected behavior.
### Recommendation
We recom... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | oracle | false | false | ## Low: Incorrect revert
### Description
`IncorrectAppearedValidators` should show `churnLimit`, but instead of it, the revert shows `_appearedValidators`: https://github.com/lidofinance/core/blob/efeff81c18f85451ebf98e8fd8bb78b8eb0095f6/contracts/0.8.9/sanity_checks/OracleReportSanityChecker.sol#L782.
### Recommenda... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | rounding | true | false | ## Low: Voting weight might not be fully utilized due to precision loss
### Description
The `_vote` method of the Voter contract votes with a given `_weight` for multiple `_stakingTokenVote` addresses, and this voting power is distributed respectively using `_weights`.
```solidity
function _vote(
uint256 _tokenId,
... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | high | cross-chain | false | false | ## High: Router liquidity on receiving chain can be double-dipped by the user
### Description
_Submitted by 0xRajeev, also found by cmichel, gpersoon, pauliax, s1m0 and shw_
During `fulfill()` on the receiving chain, if the user has set up an external contract at `txData.callTo`, the catch blocks for both `IFulfillHe... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | overflow | true | false | ## Low: Head overflow bug in `Calldata` Tuple ABI-Reencoding
### Description
There is a known security vulnerability between versions 0.5.8 - 0.8.16 of Solidity, details on it below:
The effects of the bug manifest when a contract performs ABI-encoding of a tuple that meets all of the following conditions:
- The las... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | other | false | false | ## Low: `_beforeRegisterOperator` allows invalid validator registration
### Description
The current protocol allows users to register any non-zero validator key, which is then passed as-is to the Substrate chain and stored in its validator set. However, on the Ethereum side, the protocol does not verify whether this S... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | initialization | false | false | ## Low: Active Validators Cannot Be Deactivated
### Description
A new validation node must be activated by a bot before it can receive any deposits from normal users after its initial deposit by the validator operator. Once a validating node is set as active, it is not possible to deactivate it. This may cause issues ... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | signature | false | false | ## Low: Proposers Can Bypass Prover Fee and Signature
### Description
AssignmentHooks are used to verify an assigned prover’s signature and pay the prover’s required fee from the proposer. Because the proposer can specify which assignment hooks to execute, it is possible for them to bypass both prover signature verifi... | 0 | ||
[
{
"role": "system",
"content": "You are an expert smart contract security auditor. Analyze the provided Solidity code for vulnerabilities.\n\nFor each finding, output a structured block:\nFINDING | contract: <name> | function: <name> | bug_class: <CWE/category> | confidence: <0-100>\n\nThen provide:\n- desc... | skyward_49k | low | front-running | false | false | ## Low: Rent overfunded during incremental bitmap expansion
### Description
The expand_sandwich_validators_bitmap instruction transfers enough lamports to make the account rent-exempt for the final TARGET_ACCOUNT_SIZE, even though each call may grow the account by only MAX_REALLOC_SIZE (10 KiB). If the expansion halt... | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.