oxdev/security-auditor-grpo
Text Generation • 0.5B • Updated • 1.2k
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 | gas | other | false | false | ## Gas: `<array>.length` should not be looked up in every loop of a `for`-loop
### Description
The overheads outlined below are *PER LOOP*, excluding the first loop
* storage arrays incur a Gwarmaccess (**100 gas**)
* memory arrays use `MLOAD` (**3 gas**)
* calldata arrays use `CALLDATALOAD` (**3 gas**)
Caching 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 | overflow | false | false | ## Low: Salt-counter can be exhausted
### Description
_Resolved_
The controller advances one unit of the salt value used every time a new account is deployed. After a certain number of deployments, the increment wraps into the high-order bytes that encode the address(this), producing a salt that would be able to 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 | medium | signature | true | false | ## Medium: Possible scenario for Signature Replay Attack
### Description
The `QuestFactory.mintReceipt` function mints `RabbitHoleReceipt` tokens based upon signatures signed by `claimSignerAddress`.
In the above function only the account's address and quest id values are used to generate and validate the signature.... | 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: Safety Improvements For User Funds Allocated To Unbonded Minipools
### Description
Unlike conventional minipools that require a node operator deposit of 16 ETH (MinipoolDeposit.Half), all funds staked via an unbonded minipool belong to the network’s rETH holders. As such, the two–stage `preStake()` sequence ri... | 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: Code Refactoring
### Description
## Rebalance and Refactor Plan
## Items to Address
1. Enforce a rebalance after `bank::set_utilisation_bps` is called to ensure that the lending system remains within its desired liquidity utilization range.
2. The early return in `bank::deploy` prevents fund deployment if 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 | medium | token | true | false | ## Medium: Hooklet token transfer hooks will reference the incorrect sender due to missing use of `LibMulticaller.senderOrSigner()`
### Description
**Description:** `LibMulticaller` is used throughout the codebase to retrieve the actual sender of multicall transactions; however, `BunniToken::_beforeTokenTransfer` and ... | 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 | rounding | false | false | ## High: Incorrect Reward Calculation When Reward Rate Changes
### Description
This issue has been identified within the `getRewardForStakingStore` function of the `DIAWhitelistedStaking` contract.
Currently, rewards are calculated using the current `rewardRatePerDay`, regardless of whether the rate has changed betwee... | 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 | rounding | false | false | ## High: Validators can manipulate incentive rates to receive more incentives than intended
### Description
Severity: High Risk
Context: BerachainRewardsVault.sol#L328-L330
Description: In BerachainRewardsVault.addIncentive , it's possible for anyone to arbitrarily set theincentiveR-
ate of an incentive token given 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 | other | true | false | ## Medium: `updateTp` not validating and correcting the TP
### Description
When `updateTp` is called, the provided TP value is not validated to ensure it is appropriate relative to the `openPrice` and the trade position (`buy`). Additionally, the TP is not adjusted to ensure it does not exceed the allowed maximum gain... | 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: CollateralizationOracle - misleading comments
### Description
According to an inline comment in `isOvercollateralized`, the validity status of `pcvStats` is ignored, while it is actually being checked.
Similarly, a comment in `pcvStats` mentions that the returned `protocolEquity` is 0 if there is less PCV 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 | low | other | true | false | ## Low: secp256r1 precompile uses a deprecated function
### Description
The public key validation depends on the `IsOnCurve` primitive, which was recently deprecated in Golang 1.21. The current implementation of the `secp256r1` precompile verifies that the values provided are part of the relevant elliptic curve:
```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 | high | other | false | false | ## High: A payment made towards multiple liens causes the borrower to lose funds to the payee
### Description
A payment made towards multiple liens is entirely consumed for the first one causing the borrower to lose funds to the payee.
### Impact
Only the first lien is paid off and the entire payment is sent to its 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... | skyward_49k | low | other | true | false | ## Low: `topNominees()` could consume too much gas
### Description
In `SecurityCouncilMemberElectionGovernorCountingUpgradeable.sol`, the `topNominees()` function is extremely gas-intensive due to the following reasons:
- `_compliantNominees()` copies the entire nominees array the storage of the `SecurityCouncilNomin... | 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: Enable the optimizer
### Description
**Description:** [Enable the optimizer](https://dacian.me/the-yieldoor-gas-optimizoor#heading-enabling-the-optimizer) in `foundry.toml`.
Gas results:
**Evo:**
Fixed in commit [b4fcadb](https://github.com/contractlevel/sbt/commit/b4fcadbd9c5684cc4e3b1ee3c39f72c406aaf658).... | 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: Buffer Before External Call Is Insufficient
### Description
Malicious relayers can still intentionally fail XMsgs by setting a gas limit that is just low enough. Before executing a low-level call, the `_exec()` function uses a small gas buffer of 100 gas to protect against malicious relayers intentionally settin... | 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: Missing Events
### Description
It is well\-known that events are not important *for* the contracts (and can, in fact, not even be read by a contract), but they’re important to keep “the outside world” informed about state changes and, well, events on the contracts. In general, state\-changing functions should ... | 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: Fee-on-transfer underlyings can be used to mint Illuminate PTs without fees
### Description
Fee-on-transfer underlyings can be used to mint Illuminate PTs without fees
### Impact
_Theft of unclaimed yield_
Attackers can mint free PT at the expense of Illuminate's fees.
### Recommendation
Check the actual... | 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: Unlocked Pragma
### Description
**Update**
Marked as "Fixed" by the client. Addressed in: `856ef93b20ddc24daa02e005333bc1ce9d7cbe5f`. The client provided the following explanation:
> Removed the caret from the pragma. It is now locked to version 0.8.20.
**File(s) affected:**`PowerloomToken.sol`
**Descriptio... | 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 | initialization | false | false | ## Medium: Users can claim extremely large rewards or lock rewards from LpGauge due to uninitialised poolLastUpdate variable
### Description
## Lines of code
https://github.com/code-423n4/2022-05-backd/blob/2a5664d35cde5b036074edef3c1369b984d10010/protocol/contracts/tokenomics/LpGauge.sol#L115-L119
https://github.com... | 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 | false | false | ## Gas: [06] State variables can be packed into fewer storage slots (1 instance)
### Description
Deployment. Gas Saved: **-5 008**
Minimum Method Call. Gas Saved: **1 911**
Average Method Call. Gas Saved: **15 525**
Maximum Method Call. Gas Saved: **20 972**
Overall gas change: **-62 419 (-69.524%)**
If variables... | 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: The `Trade` function doesn't use `minCollateralAmount`
### Description
[`This function`](https://github.com/Threshold-USD/dev/blob/800c6c19e44628dfda3cecaea6eedcb498bf0bf3/packages/contracts/contracts/B.Protocol/BAMM.sol#L268) can be used by mistake by someone and according to the M-1 it leads to losing mon... | 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: Lack of Governance action to update registered emitters
### Description
**Description:** The Wormhole CCTP integration contract currently exposes a function [`Governance::registerEmitterAndDomain`](https://github.com/wormhole-foundation/wormhole-circle-integration/blob/f7df33b159a71b163b8b5c7e7381c0d8f193da99/... | 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 | false | false | ## High: Isolated assets are treated as collateral in Morpho
### Description
Aave-v3 introduced isolation assets and isolation mode for users:
> "Borrowers supplying an isolated asset as collateral cannot supply other assets as collateral (though they can still supply to capture yield). Only stablecoins that have been... | 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: Bad work with decimals
### Description
6 decimals are hardcoded in the Claiming contract which can lead to incorrect work with token amounts in the future.
https://github.com/FantiumAG/smart-contracts/blob/a2d126453c1105028f12277b8f342d2cdbf01a77/contracts/claiming/FantiumClaimingV1.sol#L218-L220
### Recommen... | 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: Code Redundancy
### Description
## Code Review Summary
In `_sbt_soul_transfer`, there is an unnecessary `self.balances.remove(key)` operation in the loop that iterates over all tokens. The code first removes the key from `self.balances`, then immediately inserts a new value utilizing `self.balances.insert`, a... | 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 | true | false | ## Low: Setting NounsAuctionHouse's timeBuffer too big is possible, which will freeze bidder's funds
### Description
It's now possible to set `timeBuffer` to an arbitrary big value with `setTimeBuffer()`, there is no control:
```solidity
/**
* @notice Set the auction time buffer.
* @dev Only callable by the owner.
... | 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: NATIVE TOKEN FUNCTIONALITY COULD NOT BE USED
### Description
In the `_safeTransfer()` function from `BigBangGame.sol` smart contract, two different types of transfers could be performed. if `_token` address sent as parameter is different from 0, the function will perform a `token.transfer()`. If `_token` is `a... | 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 | access-control | false | false | ## Medium: Wrong Guard Function.
### Description
**Severity**: Medium
**Status**: Resolved
**Description**
ERC20Distribution.sol - In the purchaseTokens
assert() function was used to check the rate and balance or token. But rate and balance were calculated by parameters, so these checks can be false. assert() is... | 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: Remove needless uint8 cast
### Description
`removeParameterConstraint()`, `_addParameterConstraint()`: remove the needless uint8 cast.
https://github.com/MetaLex-Tech/borg-core/blob/9074503d37cfa1d777ef16f6c88b84c98b4f54eb/src/borgCore.sol#L418 https://github.com/MetaLex-Tech/borg-core/blob/9074503d37cfa1d777e... | 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: Missing maximum cooldown duration validation
### Description
The `cooldown_duration` value provided in `args.cooldown_duration` is directly assigned to `token_stats.cooldown_duration` without any validation. This allows users to set an excessively long cooldown period, which could negatively impact the protoco... | 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: Execution fee might not be refunded to subaccounts when updating orders
### Description
When updating an order through the **SubaccountRouter** contract, a subaccount needs to spend some gas and, sometimes, an `execution fee` that must be deposited in advance. The gas spent is refunded to the subaccount, but ... | 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 | initialization | true | false | ## Medium: ERC20TokenEmitter will not work after a certain period of time
### Description
The `timeSinceStart` in the `vrgdac.xToY` function will revert over a certain value, resulting in the `ERC20TokenEmitter#buyToken` function always revert.
### Proof of Concept
Initialize the VRGDAC using the parameters in the 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 | true | false | ## Low: [29] Wrong comment in `Diamond`
### Description
The comment `/// NOTE: expect but NOT enforce that _selectors is NON-EMPTY array` is wrong, as it is checked inside [Diamond, function `diamondCut`](https://github.com/code-423n4/2023-10-zksync/blob/c3ff020df5d11fe91209bd99d7fb0ec1272dc387/code/contracts/ethereum... | 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: `invariant` could just return false if the liquidity is zero
### Description
In the function `invariant` a check is made, so that the function will revert incase liquidity is zero.
If triggered the statement returns `(amount0 == 0 && amount1 == 0)`, so it can revert as inputted amount0 and amount1 can never be... | 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: No validation of the address parameter value in function before using this parameter in access modifiers.
### Description
At this function: https://github.com/iearn-finance/yearn-vaults/blob/54db126821c4d7aaaf5839be935cecb9b1bf088b/contracts/BaseStrategy.sol#L171
```solidity
function setStrategist(address _... | 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 | flash-loan | true | false | ## High: `removeLeverage` will attempt to send the wrong token to the user
### Description
When `removeLeverage` is called and the position is using the self-lending pod, the `_pairedAmtReceived` obtained from the unstake and remove LP process will be unwrapped from the self-lending pod. The received lending pair's sh... | 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: Precision loss due to division before multiplication
### Description
**Severity**: Low
**Status**: Resolved
**Description**
In Contract GlmManger.sol, the method `getGmTokenValueInUSDC()` has the following logic:
Here `usdcPrice` is divided by 1e18 before multiplication with (`gmTokenPrice * amount`).
Sim... | 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: Unclear code comment regarding the ability to disable and enable staking
### Description
The `EdgeChallengeManager` contract contains a code comment that suggests the staking mechanism can be disabled; however, in the current implementation, there are no functions exposing this functionality, as the staking is... | 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: Incorrect Asset Redemption in Vault Withdrawal Leading to Loss of Funds
### Description
In the TermMaxVault withdrawal functionality when the vault's asset balance is insufficient to cover the withdrawal amount, it gets funds from the order but only transfers the `amountLeft` (amountLeft -= assetBalance) inst... | 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: Max weight requirement in rebind is inaccurate
### Description
`BPool.rebind` enforces `MIN_WEIGHT` and `MAX_WEIGHT` bounds on the passed-in `denorm` value:
**code/contracts/BPool.sol:L262-L274**
```
function rebind(address token, uint balance, uint denorm)
public
\_logs\_
\_lock\_
{
require(msg.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 | medium | other | true | false | ## Medium: Staking contract is not EIP-4626 compliant
### Description
**Severity**
**Impact:** Medium
**Likelihood:** Medium
**Description**
The current staking implementation charges fees on assets deposited into the vault, as shown below:
According to [EIP4626](https://eips.ethereum.org/EIPS/eip-4626), `previe... | 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 | true | false | ## Low: Calldata Modifier is Only Valid if thecalldata is not Given by a User
### Description
The functionality in the `permittedFunctionsForLINK()` modifier (on line [175]) only restricts the function signature if the function it protects is called by a contract that doesn’t allow a user to enter the calldata. The cu... | 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 | token | true | false | Source: https://github.com/sherlock-audit/2023-02-telcoin-judging/issues/22
## Found by
jonatascm, jasonxiale, ddimitrov22, 0xGoodess, spyrosonic10
## Summary
Inside `submit()` method of `FeeBuyback.sol`, if token is `_telcoin` then it safeApprove to `_referral` contract. If `_referral` contract do not use all al... | Sherlock | 5 | Telcoin Update |
[
{
"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 | flash-loan | false | false | ## Medium: Unnecessary fee structuring
### Description
During the collateral swap [the flash loan fee is first subtracted from the flash loan amount](https://github.com/widolabs/wido-contracts/blob/d96ef2dd6a7ff3d04c44ebe87994411d1f8c84e7/contracts/compound/libraries/LibCollateralSwap.sol#L56) which is then deposited ... | 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 | rounding | true | false | ## High: The `unlockExponent` does not work as intended when it is ≠ 1
### Description
**Proof of Concept**
The documentation and the chart in `README.md` shows that it is expected that when `unlockExponent == 0` then immediately after funds `unlockDelaySec` the user can claim his whole locked amount. This is actuall... | 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: `SparseMerkleTreeVerifier` should use `Utils::_efficientKeccak` instead of duplicating the same function
### Description
**Description:** `SparseMerkleTreeVerifier` should use `Utils::_efficientKeccak` instead of duplicating the same function.
**Linea:**
Acknowledged; will be part of a future release. | 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: A risk of blocking the functionalities with whitelisting an invalid `NodeDelegator` or `Strategy`
### Description
The incorporation of `NodeDelegator` into the `LRTDepositPool` that is doesn't implement the `INodeDelegator` interface or the `Strategy` to `LRTConfig` that is not whitelisted by the Eigen Layer 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... | skyward_49k | high | liquidation | false | false | ## High: Side effects of LTV = 0 assets: Morpho's users will not be able to withdraw (collateral and "pure" supply), borrow and liquidate
### Description
When an AToken has LTV = 0, Aave restricts the usage of some operations. In particular, if the user owns at least one AToken as collateral that has LTV = 0, operatio... | 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: Last-withdrawal inflation attack
### Description
If the protocol is left with a single deposit and its funds reside on a validator, the depositor can request to withdraw all but 1 wei of shares. Because rewards accrue on the validator during the withdrawal process and settlement uses a prior share price, 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... | skyward_49k | medium | rounding | true | false | ## Medium: StableMath._calcInGivenOut may allow free swaps
### Description
The in-given-out function has rounding to calculate swaps, which could enable an attacker to obtain tokens at no cost. `StableMath._calcOutGivenOut` computes the number of tokens that one user will receive based on the number of tokens sent:
`... | 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: Fee calculation is slightly off
### Description
_Submitted by gzeon_
The fee calculation
tries to calculate a fee such that fee/(supply+fee) = %fee using a simple interest formula (i.e. no compounding), this lead to slightly less fee collected when fee are collected more frequently (small timeDiff) vs les... | 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: Cached variables not efficiently used
### Description
In `StaticATokenLM._updateRewards`, the state variable `_lifetimeRewardsClaimed` is doubly used in the following code logic when `rewardsAccrued` could simply/equally be assigned `freshRewards.wadToRay()`. This extra gas incurring behaviour is also exhibite... | 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: Interest rate decimal change can break external integrations
### Description
The `MapleLoanV5Migrator` migrates all interest rates from 18 decimals to 6 decimals. The public getter functions for these also return the rates with the new decimals, breaking existing contract integrations or off-chain dashboards.
... | 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 | Fee On Transfer | false | true |
<https://github.com/code-423n4/2022-11-redactedcartel/blob/03b71a8d395c02324cb9fdaf92401357da5b19d1/src/vaults/AutoPxGlp.sol#L367>
<https://github.com/code-423n4/2022-11-redactedcartel/blob/03b71a8d395c02324cb9fdaf92401357da5b19d1/src/PirexGmx.sol#L583>
### Impact
In `PirexGmx` and `AutoPxGlp` you have function `de... | Code4rena | 5 | Redacted Cartel |
[
{
"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: `LenderCommitmentGroup_Smart_test::addPrincipalToCommitmentGroup/burnSharesToWithdrawEarnings()` are vulnerable to slippage attacks
### Description
`LenderCommitmentGroup_Smart_test::addPrincipalToCommitmentGroup()` and `LenderCommitmentGroup_Smart_test::burnSharesToWithdrawEarnings()` are vulnerable to sli... | 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 | initialization | false | false | ## Medium: Loss of Veto Power can Lead to 51% Attack
### Description
_Submitted by TomJ, also found by 0xDjango, 0xSmartContract, Aymen0909, Ch_301, and Deivitto_
### Impact
The veto power is import functionality for current NounsDAO in order to protect their treasury from malicious proposals.
However there is ... | 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: Hardcoded addresses in contract
### Description
Addresses should not be hardcoded in contracts. Instead, they should be declared as immutable and assigned via constructor arguments. This practice keeps the code consistent across deployments on different networks and prevents the need for recompilation when add... | 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: Users Can Become Unable to Perform Unstake Requests
### Description
**Update**
Marked as "Fixed" by the client. Addressed in: `2bf732a2f1fb8dc1b80b1ba274c8a226d8e50a13`. The client provided the following explanation:
> Followed the advice as per mentioned in the audit.
The recommended check was included a... | 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 | Precision Loss | true | true | Source: https://github.com/sherlock-audit/2023-01-ajna-judging/issues/121
## Found by
berndartmueller
## Summary
Rewards may be lost (0) due to division before multiplication precision issues.
## Vulnerability Detail
The `RewardsManager._calculateNewRewards` function calculates the new rewards for a staker by fi... | Sherlock | 3.333333 | Ajna |
[
{
"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: Lack of minimum purchase protection
### Description
The PublicSale contract's `depositUSDC()` function lacks a minimum purchase guarantee mechanism. When users attempt to purchase tokens and the remaining tier cap is less than their desired amount, the contract will process a partial purchase without requiring... | 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: Missing slippage protection in sell functions
### Description
The `sellSharesByLots` and `sellSharesByUnits` functions lack slippage protection, exposing users to receiving significantly less ETH than expected when selling shares.
When a user submits a sell transaction, the payout is calculated based on 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... | solodit_api | high | Stale Price | false | true | ## Handle
hyh
## Vulnerability details
## Impact
Malicious user can monitor SetPricePerShare event and, if it was run long enough time ago and market moved, but, since there were no SetPricePerShare fired, the contract's pricePerShare is outdated, so a user can mint() with pricePerShare that is current for contract... | 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 | low | liquidation | true | false | ## Low: Inconsistency in Maintaining One-to-One Peg
### Description
## Risks in Staking with thAPT
In staking, `burn_from_thapt` and `reconcile` introduce risks that may break the intended 1:1 peg between thAPT and staked APT. thAPT is meant to be pegged 1:1 to staked APT, representing a claim on the underlying colla... | 0 |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 33
Models trained or fine-tuned on oxdev/smart-contract-security-audit-v2