Verdict is derived from severity counts via the same deterministic formula every VegaSec report uses. Unitroller.sol was scanned from etherscan verified. This is static-analysis triage, not a certification or formal audit attestation.
PDF artifact
Queued artifact pipeline · not blocking on the scan
No PDF artifact has been requested for this report yet. The HTML report and the Markdown export already carry the full disclaimer and limitations inline. PDF synthesis is a queued artifact, not part of the scan path.
Status endpoint
GET /report/solidity/VSS-20261004-ZTOB8VVZ/export.pdf
Solidity evidence report
84 audit findings
Severity distribution
Executive summary
- 84 findings surfaced (0 critical, 1 high, 23 medium, 8 low, 52 informational).
- HIGH · Unitroller.fallback() (Unitroller.sol#2586-2599) uses delegatecall to a input-controlled function id (fallback) — exploitability medium.
- Automated static analysis only. A human operator review has not been attached to this report.
Warnings (4)
- · Unmapped detector slither:erc20-interface — classified as 'other'
- · Unmapped detector slither:dead-code — classified as 'other'
- · Unmapped detector slither:unimplemented-functions — classified as 'other'
- · Unmapped detector slither:unindexed-event-address — classified as 'other'
- highAccess controlConfidence: mediumExploitability: mediumDetector: slither
Unitroller.fallback() (Unitroller.sol#2586-2599) uses delegatecall to a input-controlled function id
Evidence
Unitroller.fallback() (Unitroller.sol#2586-2599) uses delegatecall to a input-controlled function id - (success,None) = comptrollerImplementation.delegatecall(msg.data) (Unitroller.sol#2588)
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Gate privileged functions behind a tested role/ownership pattern (e.g. OpenZeppelin Ownable/AccessControl). Avoid tx.origin for authorization.
- mediumLogicConfidence: highExploitability: lowDetector: slither
CarefulMath.mulUInt(uint256,uint256) (Unitroller.sol#311-323) uses a dangerous strict equality:
Evidence
CarefulMath.mulUInt(uint256,uint256) (Unitroller.sol#311-323) uses a dangerous strict equality: - a == 0 (Unitroller.sol#312)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumLogicConfidence: highExploitability: lowDetector: slither
CarefulMath.divUInt(uint256,uint256) (Unitroller.sol#328-334) uses a dangerous strict equality:
Evidence
CarefulMath.divUInt(uint256,uint256) (Unitroller.sol#328-334) uses a dangerous strict equality: - b == 0 (Unitroller.sol#329)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumLogicConfidence: highExploitability: lowDetector: slither
Exponential.mulExp(Exponential.Exp,Exponential.Exp) (Unitroller.sol#515-535) uses a dangerous strict equality:
Evidence
Exponential.mulExp(Exponential.Exp,Exponential.Exp) (Unitroller.sol#515-535) uses a dangerous strict equality: - assert(bool)(err2 == MathError.NO_ERROR) (Unitroller.sol#532)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumOtherConfidence: highExploitability: lowDetector: slither
EIP20NonStandardInterface (Unitroller.sol#666-728) has incorrect ERC20 function interface:EIP20NonStandardInterface.transferFrom(address,address,uint256) (Unitr
Evidence
EIP20NonStandardInterface (Unitroller.sol#666-728) has incorrect ERC20 function interface:EIP20NonStandardInterface.transferFrom(address,address,uint256) (Unitroller.sol#706)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- mediumLogicConfidence: highExploitability: lowDetector: slither
CToken.constructor(ComptrollerInterface,InterestRateModel,uint256,string,string,uint256) (Unitroller.sol#1000-1028) uses a dangerous strict equality:
Evidence
CToken.constructor(ComptrollerInterface,InterestRateModel,uint256,string,string,uint256) (Unitroller.sol#1000-1028) uses a dangerous strict equality: - require(bool,string)(err == uint256(Error.NO_ERROR),Setting interest rate model failed) (Unitroller.sol#1023)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumLogicConfidence: highExploitability: lowDetector: slither
CToken.transfer(address,uint256) (Unitroller.sol#1107-1109) uses a dangerous strict equality:
Evidence
CToken.transfer(address,uint256) (Unitroller.sol#1107-1109) uses a dangerous strict equality: - transferTokens(msg.sender,msg.sender,dst,amount) == uint256(Error.NO_ERROR) (Unitroller.sol#1108)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumLogicConfidence: highExploitability: lowDetector: slither
CToken.transferFrom(address,address,uint256) (Unitroller.sol#1118-1120) uses a dangerous strict equality:
Evidence
CToken.transferFrom(address,address,uint256) (Unitroller.sol#1118-1120) uses a dangerous strict equality: - transferTokens(msg.sender,src,dst,amount) == uint256(Error.NO_ERROR) (Unitroller.sol#1119)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumLogicConfidence: highExploitability: lowDetector: slither
CToken.balanceOfUnderlying(address) (Unitroller.sol#1162-1167) uses a dangerous strict equality:
Evidence
CToken.balanceOfUnderlying(address) (Unitroller.sol#1162-1167) uses a dangerous strict equality: - require(bool)(mErr == MathError.NO_ERROR) (Unitroller.sol#1165)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumLogicConfidence: highExploitability: lowDetector: slither
CToken.supplyRatePerBlock() (Unitroller.sol#1217-1241) uses a dangerous strict equality:
Evidence
CToken.supplyRatePerBlock() (Unitroller.sol#1217-1241) uses a dangerous strict equality: - require(bool,string)(e1 == MathError.NO_ERROR,supplyRatePerBlock: calculating underlying failed) (Unitroller.sol#1229)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumLogicConfidence: highExploitability: lowDetector: slither
CToken.borrowBalanceStored(address) (Unitroller.sol#1267-1271) uses a dangerous strict equality:
Evidence
CToken.borrowBalanceStored(address) (Unitroller.sol#1267-1271) uses a dangerous strict equality: - require(bool,string)(err == MathError.NO_ERROR,borrowBalanceStored: borrowBalanceStoredInternal failed) (Unitroller.sol#1269)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumLogicConfidence: highExploitability: lowDetector: slither
CToken.exchangeRateStored() (Unitroller.sol#1324-1328) uses a dangerous strict equality:
Evidence
CToken.exchangeRateStored() (Unitroller.sol#1324-1328) uses a dangerous strict equality: - require(bool,string)(err == MathError.NO_ERROR,exchangeRateStored: exchangeRateStoredInternal failed) (Unitroller.sol#1326)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumLogicConfidence: highExploitability: lowDetector: slither
CToken.exchangeRateStoredInternal() (Unitroller.sol#1335-1364) uses a dangerous strict equality:
Evidence
CToken.exchangeRateStoredInternal() (Unitroller.sol#1335-1364) uses a dangerous strict equality: - totalSupply == 0 (Unitroller.sol#1336)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumLogicConfidence: highExploitability: lowDetector: slither
CToken.accrueInterest() (Unitroller.sol#1394-1458) uses a dangerous strict equality:
Evidence
CToken.accrueInterest() (Unitroller.sol#1394-1458) uses a dangerous strict equality: - assert(bool)(vars.mathErr == MathError.NO_ERROR) (Unitroller.sol#1409)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumUninitializedConfidence: mediumExploitability: mediumDetector: slither
CToken.accrueInterest().vars (Unitroller.sol#1395) is a local variable never initialized
Evidence
CToken.accrueInterest().vars (Unitroller.sol#1395) is a local variable never initialized
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Initialize storage variables explicitly in the constructor/initializer; for upgradeable contracts call the initializer through a tested pattern.
- mediumUninitializedConfidence: mediumExploitability: mediumDetector: slither
CToken.mintFresh(address,uint256).vars (Unitroller.sol#1504) is a local variable never initialized
Evidence
CToken.mintFresh(address,uint256).vars (Unitroller.sol#1504) is a local variable never initialized
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Initialize storage variables explicitly in the constructor/initializer; for upgradeable contracts call the initializer through a tested pattern.
- mediumLogicConfidence: highExploitability: lowDetector: slither
CToken.redeemFresh(address,uint256,uint256) (Unitroller.sol#1621-1717) uses a dangerous strict equality:
Evidence
CToken.redeemFresh(address,uint256,uint256) (Unitroller.sol#1621-1717) uses a dangerous strict equality: - require(bool,string)(vars.err == Error.NO_ERROR,redeem transfer out failed) (Unitroller.sol#1703)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumReentrancyConfidence: mediumExploitability: mediumDetector: slither
Reentrancy in CToken.redeemFresh(address,uint256,uint256) (Unitroller.sol#1621-1717):
Evidence
Reentrancy in CToken.redeemFresh(address,uint256,uint256) (Unitroller.sol#1621-1717): External calls: - allowed = comptroller.redeemAllowed(address(this),redeemer,vars.redeemTokens) (Unitroller.sol#1661) State variables written after the call(s): - totalSupply = vars.totalSupplyNew (Unitroller.sol#1706) CToken.totalSupply (Unitroller.sol#897) can be used in cross function reentrancies: - CToken.exchangeRateStoredInternal() (Unitroller.sol#1335-1364) - CToken.supplyRatePerBlock() (Unitroller.sol#1217-1241) - CToken.totalSupply (Unitroller.sol#897)
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Apply the checks-effects-interactions pattern. State writes must happen before external calls, and consider OpenZeppelin's ReentrancyGuard for high-risk entry points.
- mediumUninitializedConfidence: mediumExploitability: mediumDetector: slither
CToken.redeemFresh(address,uint256,uint256).vars (Unitroller.sol#1624) is a local variable never initialized
Evidence
CToken.redeemFresh(address,uint256,uint256).vars (Unitroller.sol#1624) is a local variable never initialized
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Initialize storage variables explicitly in the constructor/initializer; for upgradeable contracts call the initializer through a tested pattern.
- mediumLogicConfidence: highExploitability: lowDetector: slither
CToken.borrowFresh(address,uint256) (Unitroller.sol#1747-1812) uses a dangerous strict equality:
Evidence
CToken.borrowFresh(address,uint256) (Unitroller.sol#1747-1812) uses a dangerous strict equality: - require(bool,string)(vars.err == Error.NO_ERROR,borrow transfer out failed) (Unitroller.sol#1798)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumUninitializedConfidence: mediumExploitability: mediumDetector: slither
CToken.borrowFresh(address,uint256).vars (Unitroller.sol#1764) is a local variable never initialized
Evidence
CToken.borrowFresh(address,uint256).vars (Unitroller.sol#1764) is a local variable never initialized
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Initialize storage variables explicitly in the constructor/initializer; for upgradeable contracts call the initializer through a tested pattern.
- mediumLogicConfidence: highExploitability: lowDetector: slither
CToken.repayBorrowFresh(address,address,uint256) (Unitroller.sol#1862-1939) uses a dangerous strict equality:
Evidence
CToken.repayBorrowFresh(address,address,uint256) (Unitroller.sol#1862-1939) uses a dangerous strict equality: - require(bool,string)(vars.err == Error.NO_ERROR,repay borrow transfer in failed) (Unitroller.sol#1925)
Exploitability notes
Low-severity finding even at higher confidence; unlikely to be directly exploitable.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- mediumUninitializedConfidence: mediumExploitability: mediumDetector: slither
CToken.repayBorrowFresh(address,address,uint256).vars (Unitroller.sol#1874) is a local variable never initialized
Evidence
CToken.repayBorrowFresh(address,address,uint256).vars (Unitroller.sol#1874) is a local variable never initialized
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Initialize storage variables explicitly in the constructor/initializer; for upgradeable contracts call the initializer through a tested pattern.
- mediumReentrancyConfidence: mediumExploitability: mediumDetector: slither
Reentrancy in CToken.liquidateBorrowInternal(address,uint256,CToken) (Unitroller.sol#1949-1964):
Evidence
Reentrancy in CToken.liquidateBorrowInternal(address,uint256,CToken) (Unitroller.sol#1949-1964): External calls: - error = cTokenCollateral.accrueInterest() (Unitroller.sol#1956) - liquidateBorrowFresh(msg.sender,borrower,repayAmount,cTokenCollateral) (Unitroller.sol#1963) - allowed = comptroller.repayBorrowAllowed(address(this),payer,borrower,repayAmount) (Unitroller.sol#1864) - allowed = comptroller.liquidateBorrowAllowed(address(this),address(cTokenCollateral),liquidator,borrower,repayAmount) (Unitroller.sol#1977) - seizeError = cTokenCollateral.seize(liquidator,borrower,seizeTokens) (Unitroller.sol#2025) - comptroller.liquidateBorrowVerify(address(this),address(cTokenCollateral),liquidator,borrower,repayAmount,seizeTokens) (Unitroller.sol#2032) - comptroller.repayBorrowVerify(address(this),payer,borrower,vars.repayAmount,vars.borrowerIndex) (Unitroller.sol#1936) State variables written after the call(s): - liquidateBorrowFresh(msg.sender,borrower,repayAmount,cTokenCollateral) (Unitroller.sol#1963) - totalBorrows = vars.totalBorrowsNew (Unitroller.sol#1930) CToken.totalBorrows (Unitroller.sol#887) can be used in cross function reentrancies: - CToken.accrueInterest() (Unitroller.sol#1394-1458) - CToken.borrowRatePerBlock() (Unitroller.sol#1207-1211) - CToken.exchangeRateStoredInternal() (Unitroller.sol#1335-1364) - CToken.supplyRatePerBlock() (Unitroller.sol#1217-1241) - CToken.totalBorrows (Unitroller.sol#887)
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Apply the checks-effects-interactions pattern. State writes must happen before external calls, and consider OpenZeppelin's ReentrancyGuard for high-risk entry points.
- lowReentrancyConfidence: mediumExploitability: mediumDetector: slither
Reentrancy in CToken.mintFresh(address,uint256) (Unitroller.sol#1492-1569):
Evidence
Reentrancy in CToken.mintFresh(address,uint256) (Unitroller.sol#1492-1569): External calls: - allowed = comptroller.mintAllowed(address(this),minter,mintAmount) (Unitroller.sol#1494) Event emitted after the call(s): - Failure(uint256(err),uint256(info),0) (Unitroller.sol#193) - fail(Error.MARKET_NOT_FRESH,FailureInfo.MINT_FRESHNESS_CHECK) (Unitroller.sol#1501) - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.MATH_ERROR,FailureInfo.MINT_NEW_ACCOUNT_BALANCE_CALCULATION_FAILED,uint256(vars.mathErr)) (Unitroller.sol#1538) - Failure(uint256(err),uint256(info),0) (Unitroller.sol#193) - fail(vars.err,FailureInfo.MINT_TRANSFER_IN_NOT_POSSIBLE) (Unitroller.sol#1509) - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.MATH_ERROR,FailureInfo.MINT_EXCHANGE_CALCULATION_FAILED,uint256(vars.mathErr)) (Unitroller.sol#1523) - Failure(uint256(err),uint256(info),0) (Unitroller.sol#193) - fail(vars.err,FailureInfo.MINT_TRANSFER_IN_FAILED) (Unitroller.sol#1554) - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.COMPTROLLER_REJECTION,FailureInfo.MINT_COMPTROLLER_REJECTION,allowed) (Unitroller.sol#1496) - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.MATH_ERROR,FailureInfo.MINT_NEW_TOTAL_SUPPLY_CALCULATION_FAILED,uint256(vars.mathErr)) (Unitroller.sol#1533) - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.MATH_ERROR,FailureInfo.MINT_EXCHANGE_RATE_READ_FAILED,uint256(vars.mathErr)) (Unitroller.sol#1518) - Mint(minter,mintAmount,vars.mintTokens) (Unitroller.sol#1562) - Transfer(address(this),minter,vars.mintTokens) (Unitroller.sol#1563)
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Apply the checks-effects-interactions pattern. State writes must happen before external calls, and consider OpenZeppelin's ReentrancyGuard for high-risk entry points.
- lowReentrancyConfidence: mediumExploitability: mediumDetector: slither
Reentrancy in CToken.redeemFresh(address,uint256,uint256) (Unitroller.sol#1621-1717):
Evidence
Reentrancy in CToken.redeemFresh(address,uint256,uint256) (Unitroller.sol#1621-1717): External calls: - allowed = comptroller.redeemAllowed(address(this),redeemer,vars.redeemTokens) (Unitroller.sol#1661) Event emitted after the call(s): - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.MATH_ERROR,FailureInfo.REDEEM_NEW_ACCOUNT_BALANCE_CALCULATION_FAILED,uint256(vars.mathErr)) (Unitroller.sol#1683) - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.MATH_ERROR,FailureInfo.REDEEM_NEW_TOTAL_SUPPLY_CALCULATION_FAILED,uint256(vars.mathErr)) (Unitroller.sol#1678) - Failure(uint256(err),uint256(info),0) (Unitroller.sol#193) - fail(Error.TOKEN_INSUFFICIENT_CASH,FailureInfo.REDEEM_TRANSFER_OUT_NOT_POSSIBLE) (Unitroller.sol#1688) - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.COMPTROLLER_REJECTION,FailureInfo.REDEEM_COMPTROLLER_REJECTION,allowed) (Unitroller.sol#1663) - Failure(uint256(err),uint256(info),0) (Unitroller.sol#193) - fail(Error.MARKET_NOT_FRESH,FailureInfo.REDEEM_FRESHNESS_CHECK) (Unitroller.sol#1668) - Redeem(redeemer,vars.redeemAmount,vars.redeemTokens) (Unitroller.sol#1711) - Transfer(redeemer,address(this),vars.redeemTokens) (Unitroller.sol#1710)
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Apply the checks-effects-interactions pattern. State writes must happen before external calls, and consider OpenZeppelin's ReentrancyGuard for high-risk entry points.
- lowReentrancyConfidence: mediumExploitability: mediumDetector: slither
Reentrancy in CToken.borrowFresh(address,uint256) (Unitroller.sol#1747-1812):
Evidence
Reentrancy in CToken.borrowFresh(address,uint256) (Unitroller.sol#1747-1812): External calls: - allowed = comptroller.borrowAllowed(address(this),borrower,borrowAmount) (Unitroller.sol#1749) Event emitted after the call(s): - Borrow(borrower,borrowAmount,vars.accountBorrowsNew,vars.totalBorrowsNew) (Unitroller.sol#1806) - Failure(uint256(err),uint256(info),0) (Unitroller.sol#193) - fail(Error.MARKET_NOT_FRESH,FailureInfo.BORROW_FRESHNESS_CHECK) (Unitroller.sol#1756) - Failure(uint256(err),uint256(info),0) (Unitroller.sol#193) - fail(Error.TOKEN_INSUFFICIENT_CASH,FailureInfo.BORROW_CASH_NOT_AVAILABLE) (Unitroller.sol#1761) - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.MATH_ERROR,FailureInfo.BORROW_ACCUMULATED_BALANCE_CALCULATION_FAILED,uint256(vars.mathErr)) (Unitroller.sol#1773) - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.MATH_ERROR,FailureInfo.BORROW_NEW_ACCOUNT_BORROW_BALANCE_CALCULATION_FAILED,uint256(vars.mathErr)) (Unitroller.sol#1778) - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.MATH_ERROR,FailureInfo.BORROW_NEW_TOTAL_BALANCE_CALCULATION_FAILED,uint256(vars.mathErr)) (Unitroller.sol#1783) - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.COMPTROLLER_REJECTION,FailureInfo.BORROW_COMPTROLLER_REJECTION,allowed) (Unitroller.sol#1751)
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Apply the checks-effects-interactions pattern. State writes must happen before external calls, and consider OpenZeppelin's ReentrancyGuard for high-risk entry points.
- lowReentrancyConfidence: mediumExploitability: mediumDetector: slither
Reentrancy in CToken.repayBorrowFresh(address,address,uint256) (Unitroller.sol#1862-1939):
Evidence
Reentrancy in CToken.repayBorrowFresh(address,address,uint256) (Unitroller.sol#1862-1939): External calls: - allowed = comptroller.repayBorrowAllowed(address(this),payer,borrower,repayAmount) (Unitroller.sol#1864) Event emitted after the call(s): - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.COMPTROLLER_REJECTION,FailureInfo.REPAY_BORROW_COMPTROLLER_REJECTION,allowed) (Unitroller.sol#1866) - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.MATH_ERROR,FailureInfo.REPAY_BORROW_ACCUMULATED_BALANCE_CALCULATION_FAILED,uint256(vars.mathErr)) (Unitroller.sol#1882) - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.MATH_ERROR,FailureInfo.REPAY_BORROW_NEW_ACCOUNT_BORROW_BALANCE_CALCULATION_FAILED,uint256(vars.mathErr)) (Unitroller.sol#1905) - Failure(uint256(err),uint256(info),0) (Unitroller.sol#193) - fail(vars.err,FailureInfo.REPAY_BORROW_TRANSFER_IN_NOT_POSSIBLE) (Unitroller.sol#1895) - Failure(uint256(err),uint256(info),0) (Unitroller.sol#193) - fail(Error.MARKET_NOT_FRESH,FailureInfo.REPAY_BORROW_FRESHNESS_CHECK) (Unitroller.sol#1871) - Failure(uint256(err),uint256(info),opaqueError) (Unitroller.sol#202) - failOpaque(Error.MATH_ERROR,FailureInfo.REPAY_BORROW_NEW_TOTAL_BALANCE_CALCULATION_FAILED,uint256(vars.mathErr)) (Unitroller.sol#1910) - RepayBorrow(payer,borrower,vars.repayAmount,vars.accountBorrowsNew,vars.totalBorrowsNew) (Unitroller.sol#1933)
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Apply the checks-effects-interactions pattern. State writes must happen before external calls, and consider OpenZeppelin's ReentrancyGuard for high-risk entry points.
- lowReentrancyConfidence: mediumExploitability: mediumDetector: slither
Reentrancy in CToken.liquidateBorrowFresh(address,address,uint256,CToken) (Unitroller.sol#1975-2035):
Evidence
Reentrancy in CToken.liquidateBorrowFresh(address,address,uint256,CToken) (Unitroller.sol#1975-2035): External calls: - allowed = comptroller.liquidateBorrowAllowed(address(this),address(cTokenCollateral),liquidator,borrower,repayAmount) (Unitroller.sol#1977) - repayBorrowError = repayBorrowFresh(liquidator,borrower,repayAmount) (Unitroller.sol#2019) - allowed = comptroller.repayBorrowAllowed(address(this),payer,borrower,repayAmount) (Unitroller.sol#1864) - comptroller.repayBorrowVerify(address(this),payer,borrower,vars.repayAmount,vars.borrowerIndex) (Unitroller.sol#1936) - seizeError = cTokenCollateral.seize(liquidator,borrower,seizeTokens) (Unitroller.sol#2025) Event emitted after the call(s): - LiquidateBorrow(liquidator,borrower,repayAmount,address(cTokenCollateral),seizeTokens) (Unitroller.sol#2029)
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Apply the checks-effects-interactions pattern. State writes must happen before external calls, and consider OpenZeppelin's ReentrancyGuard for high-risk entry points.
- lowAccess controlConfidence: mediumExploitability: mediumDetector: slither
CToken._setPendingAdmin(address).newPendingAdmin (Unitroller.sol#2105) lacks a zero-check on :
Evidence
CToken._setPendingAdmin(address).newPendingAdmin (Unitroller.sol#2105) lacks a zero-check on : - pendingAdmin = newPendingAdmin (Unitroller.sol#2115)
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Gate privileged functions behind a tested role/ownership pattern (e.g. OpenZeppelin Ownable/AccessControl). Avoid tx.origin for authorization.
- lowAccess controlConfidence: mediumExploitability: mediumDetector: slither
Unitroller._setPendingImplementation(address).newPendingImplementation (Unitroller.sol#2487) lacks a zero-check on :
Evidence
Unitroller._setPendingImplementation(address).newPendingImplementation (Unitroller.sol#2487) lacks a zero-check on : - pendingComptrollerImplementation = newPendingImplementation (Unitroller.sol#2495)
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Gate privileged functions behind a tested role/ownership pattern (e.g. OpenZeppelin Ownable/AccessControl). Avoid tx.origin for authorization.
- lowAccess controlConfidence: mediumExploitability: mediumDetector: slither
Unitroller._setPendingAdmin(address).newPendingAdmin (Unitroller.sol#2536) lacks a zero-check on :
Evidence
Unitroller._setPendingAdmin(address).newPendingAdmin (Unitroller.sol#2536) lacks a zero-check on : - pendingAdmin = newPendingAdmin (Unitroller.sol#2546)
Exploitability notes
Medium-confidence detection; manual review required before relying on the finding either way.
Remediation
Gate privileged functions behind a tested role/ownership pattern (e.g. OpenZeppelin Ownable/AccessControl). Avoid tx.origin for authorization.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Version constraint ^0.5.8 contains known severe issues (https://solidity.readthedocs.io/en/latest/bugs.html)
Evidence
Version constraint ^0.5.8 contains known severe issues (https://solidity.readthedocs.io/en/latest/bugs.html) - AbiReencodingHeadOverflowWithStaticArrayCleanup - DirtyBytesArrayToStorage - NestedCalldataArrayAbiReencodingSizeValidation - ABIDecodeTwoDimensionalArrayMemory - KeccakCaching - EmptyByteArrayCopy - DynamicArrayCleanup - ImplicitConstructorCallvalueCheck - TupleAssignmentMultiStackSlotComponents - MemoryArrayCreationOverflow - privateCanBeOverridden - YulOptimizerRedundantAssignmentBreakContinue0.5 - ABIEncoderV2CalldataStructsWithStaticallySizedAndDynamicallyEncodedMembers - SignedArrayStorageCopy - ABIEncoderV2StorageArrayWithMultiSlotElement - DynamicConstructorArgumentsClippedABIV2. It is used by: - ^0.5.8 (Unitroller.sol#3) - ^0.5.8 (Unitroller.sol#210) - ^0.5.8 (Unitroller.sol#288) - ^0.5.8 (Unitroller.sol#376) - ^0.5.8 (Unitroller.sol#597) - ^0.5.8 (Unitroller.sol#659) - ^0.5.8 (Unitroller.sol#732) - ^0.5.8 (Unitroller.sol#767) - ^0.5.8 (Unitroller.sol#799) - ^0.5.8 (Unitroller.sol#2373) - ^0.5.8 (Unitroller.sol#2393) - ^0.5.8 (Unitroller.sol#2450)
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
ComptrollerErrorReporter.failOpaque(ComptrollerErrorReporter.Error,ComptrollerErrorReporter.FailureInfo,uint256) (Unitroller.sol#68-72) is never used and should
Evidence
ComptrollerErrorReporter.failOpaque(ComptrollerErrorReporter.Error,ComptrollerErrorReporter.FailureInfo,uint256) (Unitroller.sol#68-72) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Constant Exponential.expScale (Unitroller.sol#387) is not in UPPER_CASE_WITH_UNDERSCORES
Evidence
Constant Exponential.expScale (Unitroller.sol#387) is not in UPPER_CASE_WITH_UNDERSCORES
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Constant Exponential.halfExpScale (Unitroller.sol#388) is not in UPPER_CASE_WITH_UNDERSCORES
Evidence
Constant Exponential.halfExpScale (Unitroller.sol#388) is not in UPPER_CASE_WITH_UNDERSCORES
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Constant Exponential.mantissaOne (Unitroller.sol#389) is not in UPPER_CASE_WITH_UNDERSCORES
Evidence
Constant Exponential.mantissaOne (Unitroller.sol#389) is not in UPPER_CASE_WITH_UNDERSCORES
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
Exponential.addExp(Exponential.Exp,Exponential.Exp) (Unitroller.sol#417-421) is never used and should be removed
Evidence
Exponential.addExp(Exponential.Exp,Exponential.Exp) (Unitroller.sol#417-421) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
Exponential.divScalar(Exponential.Exp,uint256) (Unitroller.sol#471-478) is never used and should be removed
Evidence
Exponential.divScalar(Exponential.Exp,uint256) (Unitroller.sol#471-478) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
Exponential.divScalarByExpTruncate(uint256,Exponential.Exp) (Unitroller.sol#503-510) is never used and should be removed
Evidence
Exponential.divScalarByExpTruncate(uint256,Exponential.Exp) (Unitroller.sol#503-510) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
Exponential.mulExp(uint256,uint256) (Unitroller.sol#540-542) is never used and should be removed
Evidence
Exponential.mulExp(uint256,uint256) (Unitroller.sol#540-542) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
Exponential.divExp(Exponential.Exp,Exponential.Exp) (Unitroller.sol#560-562) is never used and should be removed
Evidence
Exponential.divExp(Exponential.Exp,Exponential.Exp) (Unitroller.sol#560-562) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
Exponential.lessThanExp(Exponential.Exp,Exponential.Exp) (Unitroller.sol#576-578) is never used and should be removed
Evidence
Exponential.lessThanExp(Exponential.Exp,Exponential.Exp) (Unitroller.sol#576-578) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
Exponential.lessThanOrEqualExp(Exponential.Exp,Exponential.Exp) (Unitroller.sol#583-585) is never used and should be removed
Evidence
Exponential.lessThanOrEqualExp(Exponential.Exp,Exponential.Exp) (Unitroller.sol#583-585) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
Exponential.isZeroExp(Exponential.Exp) (Unitroller.sol#590-592) is never used and should be removed
Evidence
Exponential.isZeroExp(Exponential.Exp) (Unitroller.sol#590-592) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: highExploitability: lowDetector: slither
CToken (Unitroller.sol#813-2369) does not implement functions:
Evidence
CToken (Unitroller.sol#813-2369) does not implement functions: - CToken.checkTransferIn(address,uint256) (Unitroller.sol#2354) - CToken.doTransferIn(address,uint256) (Unitroller.sol#2361) - CToken.doTransferOut(address,uint256) (Unitroller.sol#2368) - CToken.getCashPrior() (Unitroller.sol#2348)
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Constant CToken.borrowRateMaxMantissa (Unitroller.sol#837) is not in UPPER_CASE_WITH_UNDERSCORES
Evidence
Constant CToken.borrowRateMaxMantissa (Unitroller.sol#837) is not in UPPER_CASE_WITH_UNDERSCORES
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Constant CToken.reserveFactorMaxMantissa (Unitroller.sol#842) is not in UPPER_CASE_WITH_UNDERSCORES
Evidence
Constant CToken.reserveFactorMaxMantissa (Unitroller.sol#842) is not in UPPER_CASE_WITH_UNDERSCORES
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalOtherConfidence: highExploitability: lowDetector: slither
Event CToken.Mint(address,uint256,uint256) (Unitroller.sol#935) has address parameters but no indexed parameters
Evidence
Event CToken.Mint(address,uint256,uint256) (Unitroller.sol#935) has address parameters but no indexed parameters
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: highExploitability: lowDetector: slither
Event CToken.Redeem(address,uint256,uint256) (Unitroller.sol#940) has address parameters but no indexed parameters
Evidence
Event CToken.Redeem(address,uint256,uint256) (Unitroller.sol#940) has address parameters but no indexed parameters
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: highExploitability: lowDetector: slither
Event CToken.Borrow(address,uint256,uint256,uint256) (Unitroller.sol#945) has address parameters but no indexed parameters
Evidence
Event CToken.Borrow(address,uint256,uint256,uint256) (Unitroller.sol#945) has address parameters but no indexed parameters
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: highExploitability: lowDetector: slither
Event CToken.RepayBorrow(address,address,uint256,uint256,uint256) (Unitroller.sol#950) has address parameters but no indexed parameters
Evidence
Event CToken.RepayBorrow(address,address,uint256,uint256,uint256) (Unitroller.sol#950) has address parameters but no indexed parameters
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: highExploitability: lowDetector: slither
Event CToken.LiquidateBorrow(address,address,uint256,address,uint256) (Unitroller.sol#955) has address parameters but no indexed parameters
Evidence
Event CToken.LiquidateBorrow(address,address,uint256,address,uint256) (Unitroller.sol#955) has address parameters but no indexed parameters
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: highExploitability: lowDetector: slither
Event CToken.NewPendingAdmin(address,address) (Unitroller.sol#963) has address parameters but no indexed parameters
Evidence
Event CToken.NewPendingAdmin(address,address) (Unitroller.sol#963) has address parameters but no indexed parameters
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: highExploitability: lowDetector: slither
Event CToken.NewAdmin(address,address) (Unitroller.sol#968) has address parameters but no indexed parameters
Evidence
Event CToken.NewAdmin(address,address) (Unitroller.sol#968) has address parameters but no indexed parameters
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: highExploitability: lowDetector: slither
Event CToken.ReservesReduced(address,uint256,uint256) (Unitroller.sol#988) has address parameters but no indexed parameters
Evidence
Event CToken.ReservesReduced(address,uint256,uint256) (Unitroller.sol#988) has address parameters but no indexed parameters
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
CToken.mintInternal(uint256) (Unitroller.sol#1466-1474) is never used and should be removed
Evidence
CToken.mintInternal(uint256) (Unitroller.sol#1466-1474) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
CToken.mintFresh(address,uint256) (Unitroller.sol#1492-1569) is never used and should be removed
Evidence
CToken.mintFresh(address,uint256) (Unitroller.sol#1492-1569) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
CToken.redeemInternal(uint256) (Unitroller.sol#1577-1585) is never used and should be removed
Evidence
CToken.redeemInternal(uint256) (Unitroller.sol#1577-1585) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
CToken.redeemUnderlyingInternal(uint256) (Unitroller.sol#1593-1601) is never used and should be removed
Evidence
CToken.redeemUnderlyingInternal(uint256) (Unitroller.sol#1593-1601) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
CToken.redeemFresh(address,uint256,uint256) (Unitroller.sol#1621-1717) is never used and should be removed
Evidence
CToken.redeemFresh(address,uint256,uint256) (Unitroller.sol#1621-1717) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
CToken.borrowInternal(uint256) (Unitroller.sol#1724-1732) is never used and should be removed
Evidence
CToken.borrowInternal(uint256) (Unitroller.sol#1724-1732) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
CToken.borrowFresh(address,uint256) (Unitroller.sol#1747-1812) is never used and should be removed
Evidence
CToken.borrowFresh(address,uint256) (Unitroller.sol#1747-1812) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
CToken.repayBorrowInternal(uint256) (Unitroller.sol#1819-1827) is never used and should be removed
Evidence
CToken.repayBorrowInternal(uint256) (Unitroller.sol#1819-1827) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
CToken.repayBorrowBehalfInternal(address,uint256) (Unitroller.sol#1835-1843) is never used and should be removed
Evidence
CToken.repayBorrowBehalfInternal(address,uint256) (Unitroller.sol#1835-1843) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
CToken.repayBorrowFresh(address,address,uint256) (Unitroller.sol#1862-1939) is never used and should be removed
Evidence
CToken.repayBorrowFresh(address,address,uint256) (Unitroller.sol#1862-1939) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
CToken.liquidateBorrowInternal(address,uint256,CToken) (Unitroller.sol#1949-1964) is never used and should be removed
Evidence
CToken.liquidateBorrowInternal(address,uint256,CToken) (Unitroller.sol#1949-1964) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: mediumExploitability: lowDetector: slither
CToken.liquidateBorrowFresh(address,address,uint256,CToken) (Unitroller.sol#1975-2035) is never used and should be removed
Evidence
CToken.liquidateBorrowFresh(address,address,uint256,CToken) (Unitroller.sol#1975-2035) is never used and should be removed
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Function CToken._setPendingAdmin(address) (Unitroller.sol#2105-2121) is not in mixedCase
Evidence
Function CToken._setPendingAdmin(address) (Unitroller.sol#2105-2121) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Function CToken._acceptAdmin() (Unitroller.sol#2128-2148) is not in mixedCase
Evidence
Function CToken._acceptAdmin() (Unitroller.sol#2128-2148) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Function CToken._setComptroller(ComptrollerInterface) (Unitroller.sol#2155-2172) is not in mixedCase
Evidence
Function CToken._setComptroller(ComptrollerInterface) (Unitroller.sol#2155-2172) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Function CToken._setReserveFactor(uint256) (Unitroller.sol#2179-2187) is not in mixedCase
Evidence
Function CToken._setReserveFactor(uint256) (Unitroller.sol#2179-2187) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Function CToken._reduceReserves(uint256) (Unitroller.sol#2224-2232) is not in mixedCase
Evidence
Function CToken._reduceReserves(uint256) (Unitroller.sol#2224-2232) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Function CToken._setInterestRateModel(InterestRateModel) (Unitroller.sol#2294-2302) is not in mixedCase
Evidence
Function CToken._setInterestRateModel(InterestRateModel) (Unitroller.sol#2294-2302) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalOtherConfidence: highExploitability: lowDetector: slither
Event Unitroller.NewPendingImplementation(address,address) (Unitroller.sol#2464) has address parameters but no indexed parameters
Evidence
Event Unitroller.NewPendingImplementation(address,address) (Unitroller.sol#2464) has address parameters but no indexed parameters
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: highExploitability: lowDetector: slither
Event Unitroller.NewImplementation(address,address) (Unitroller.sol#2469) has address parameters but no indexed parameters
Evidence
Event Unitroller.NewImplementation(address,address) (Unitroller.sol#2469) has address parameters but no indexed parameters
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: highExploitability: lowDetector: slither
Event Unitroller.NewPendingAdmin(address,address) (Unitroller.sol#2474) has address parameters but no indexed parameters
Evidence
Event Unitroller.NewPendingAdmin(address,address) (Unitroller.sol#2474) has address parameters but no indexed parameters
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalOtherConfidence: highExploitability: lowDetector: slither
Event Unitroller.NewAdmin(address,address) (Unitroller.sol#2479) has address parameters but no indexed parameters
Evidence
Event Unitroller.NewAdmin(address,address) (Unitroller.sol#2479) has address parameters but no indexed parameters
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Review the detector output against the source manually; if exploitable, design a fix and add a regression test before deploying.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Function Unitroller._setPendingImplementation(address) (Unitroller.sol#2487-2500) is not in mixedCase
Evidence
Function Unitroller._setPendingImplementation(address) (Unitroller.sol#2487-2500) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Function Unitroller._acceptImplementation() (Unitroller.sol#2507-2525) is not in mixedCase
Evidence
Function Unitroller._acceptImplementation() (Unitroller.sol#2507-2525) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Function Unitroller._setPendingAdmin(address) (Unitroller.sol#2536-2552) is not in mixedCase
Evidence
Function Unitroller._setPendingAdmin(address) (Unitroller.sol#2536-2552) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Function Unitroller._acceptAdmin() (Unitroller.sol#2559-2579) is not in mixedCase
Evidence
Function Unitroller._acceptAdmin() (Unitroller.sol#2559-2579) is not in mixedCase
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalLogicConfidence: highExploitability: lowDetector: slither
Unitroller.fallback() (Unitroller.sol#2586-2599) uses assembly
Evidence
Unitroller.fallback() (Unitroller.sol#2586-2599) uses assembly - INLINE ASM (Unitroller.sol#2591-2598)
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Re-derive the business rule by hand, write a property-based test that fails on the current path, and only then fix the implementation.
- informationalUnchecked callConfidence: highExploitability: lowDetector: slither
Low level call in Unitroller.fallback() (Unitroller.sol#2586-2599):
Evidence
Low level call in Unitroller.fallback() (Unitroller.sol#2586-2599): - (success,None) = comptrollerImplementation.delegatecall(msg.data) (Unitroller.sol#2588)
Exploitability notes
Informational signal; not directly exploitable without additional context.
Remediation
Check the boolean return of low-level call/delegatecall/send and revert on failure with a descriptive reason string.
Exploit reasoning
Reference-grade reasoning tied to evidence
- 47714bc3f62d1dc1657d68c427f75a5c8f7159e7b1453344d0278f8ed4c93fb0 · access-controlhighConfidence: low
Conditions point at the exploit but at least one precondition needs operator confirmation.
Preconditions
- Sensitive function lacks an explicit caller restriction or relies on tx.origin
- Caller controls the path that reaches the function
Action
Attacker calls the unprotected function from an attacker-controlled address, bypassing the intended restriction.
Impact
Unauthorized state mutation: ownership transfer, parameter changes, balance writes, or admin-only operations executed by a non-admin.
False-positive caveats
- The function may be intentionally callable by anyone (e.g. a public mint with a price guard).
- Access control may live in a modifier the analyzer did not parse.
Remediation checklist
- Replace tx.origin checks with msg.sender against a role registry.
- Add a `onlyRole(...)` or equivalent modifier from a vetted access control library.
- Add unit tests that assert non-admin callers revert.
- c58aa21c96043e1138a136fa5121c5b0e20e5fbf2b345eeae5a37877d9af6cfc · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- 621c896ac1a4a55914cfb05d283c1959f768894e80de14c4ff027955bc971af2 · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- 5d3e639e66230f1dc4c819d7a2b1784a3331c76d6068b0a08c56443012711a7c · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- 470160b8998b07d1718bb884be18143453560a4112acfbe54e7b9d91375c4801 · othermedium
Not determined
Question: Is this finding exploitable in this specific contract?
Reason: Finding class is 'other'; no deterministic narrative is safe without operator review.
- 0c39f7a11bd6b0730a69feece7c184d1404efe811ff8b8e1e6c8fd92a1a4a782 · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- 51424ac06037bf29dbbdc3805d99e57763fabc19c68c1b5085fd374aa822d0a8 · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- 466be0c856872b54b8bf12cc5d32bfa16020fae8a4b1d446ceede0062383e9d3 · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- a5f5f07422ae14f74fc24263bff9ebf89fdf08d73dc74ff13eb399ec1b8c1a00 · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- 3a8b64ee09e7e8853bfc1fac1e3717507dc85b56256bc31ee870d1dc4cbac64e · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- ad74e062fc82f781ebcfcd418eb94fae3e8f63cc21568f192f707f06bf1dad64 · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- 7873f2c074712af7d64e6cad5efe85a06e900230c4200cc86923b336bd00aae9 · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- e5cb00eadea83a14bccaadc8380b2c84749be92faee2e6c306a9f18e2accd6e7 · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- 21c8514a55dbfa5c0e1cd696d3a438fe48850b9f6b712bd614f0ea5fb98cc78a · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- 6ea66fb7f3767aa2397d0eef2bf80971a455e46b02ce8b0dd293fc1d85d152cd · uninitializedmediumConfidence: low
Conditions point at the exploit but at least one precondition needs operator confirmation.
Preconditions
- Storage variable used before being set in the constructor or initialize() function
- Upgradeable contract whose initialize() was not called
Action
Attacker calls initialize() (or relies on the default zero value) to set themselves as owner / admin.
Impact
Full takeover of the proxy or unbounded admin power.
False-positive caveats
- The contract may be deployed with the initializer invoked atomically by a factory.
- Default zero values may be intentional for the variable's semantics.
Remediation checklist
- Require initialize() to be called exactly once via OpenZeppelin Initializable.
- Disable initializers in the implementation constructor for upgradeable proxies.
- Add a deployment test that fails if initialize() is callable post-deployment.
- 5aa49507ce252bdf2e518a43ba1ec0903ffcc22ec9a90ee9e05783f0b41fb2f2 · uninitializedmediumConfidence: low
Conditions point at the exploit but at least one precondition needs operator confirmation.
Preconditions
- Storage variable used before being set in the constructor or initialize() function
- Upgradeable contract whose initialize() was not called
Action
Attacker calls initialize() (or relies on the default zero value) to set themselves as owner / admin.
Impact
Full takeover of the proxy or unbounded admin power.
False-positive caveats
- The contract may be deployed with the initializer invoked atomically by a factory.
- Default zero values may be intentional for the variable's semantics.
Remediation checklist
- Require initialize() to be called exactly once via OpenZeppelin Initializable.
- Disable initializers in the implementation constructor for upgradeable proxies.
- Add a deployment test that fails if initialize() is callable post-deployment.
- d02fc4b8c5b0d6e0e2a9f88a480c88f0ba9bfdb10992c536aef1bf3628eb7736 · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- d22b8033a04044e1fec23a78e74fa43e56c27e4480f5b03c6a05b8d63dda7648 · reentrancymediumConfidence: low
Conditions point at the exploit but at least one precondition needs operator confirmation.
Preconditions
- External call to an untrusted address before the contract's own state is updated
- Contract or callback path reachable from the external caller
- No nonReentrant guard or equivalent on the entry-point function
Action
Attacker contract receives control during the external call and re-enters the original function before the original state write completes, repeating the state-changing side effect.
Impact
Duplicated withdrawals, double-spend on accounting balances, or out-of-order updates to invariants the function relies on.
False-positive caveats
- The external call may be to a known, trusted contract whose behavior is provable.
- The function may be guarded indirectly by a flag or external lock not visible to the analyzer.
Remediation checklist
- Apply checks-effects-interactions: update internal state before any external call.
- Add a nonReentrant guard on the entry-point function.
- Where feasible, pull-payment instead of push-payment on user balances.
- 0e6013ae9f6b6aff463d84aa42918c7e5bdea7ca10adb933399a5c0e1e594918 · uninitializedmediumConfidence: low
Conditions point at the exploit but at least one precondition needs operator confirmation.
Preconditions
- Storage variable used before being set in the constructor or initialize() function
- Upgradeable contract whose initialize() was not called
Action
Attacker calls initialize() (or relies on the default zero value) to set themselves as owner / admin.
Impact
Full takeover of the proxy or unbounded admin power.
False-positive caveats
- The contract may be deployed with the initializer invoked atomically by a factory.
- Default zero values may be intentional for the variable's semantics.
Remediation checklist
- Require initialize() to be called exactly once via OpenZeppelin Initializable.
- Disable initializers in the implementation constructor for upgradeable proxies.
- Add a deployment test that fails if initialize() is callable post-deployment.
- e80f8eb2e0c36ec76685d7d4ad80d771d84d478b8f3443c8e69fa3e7e2d1873e · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- dfaba343324115e9f2167fca3e0f76ff12f0cbcd64908e7e12f014eb7eee39a3 · uninitializedmediumConfidence: low
Conditions point at the exploit but at least one precondition needs operator confirmation.
Preconditions
- Storage variable used before being set in the constructor or initialize() function
- Upgradeable contract whose initialize() was not called
Action
Attacker calls initialize() (or relies on the default zero value) to set themselves as owner / admin.
Impact
Full takeover of the proxy or unbounded admin power.
False-positive caveats
- The contract may be deployed with the initializer invoked atomically by a factory.
- Default zero values may be intentional for the variable's semantics.
Remediation checklist
- Require initialize() to be called exactly once via OpenZeppelin Initializable.
- Disable initializers in the implementation constructor for upgradeable proxies.
- Add a deployment test that fails if initialize() is callable post-deployment.
- d1c99438d1e1811698369b7ce050398d9192c922c66bc69aa650bc523d110930 · logicmediumConfidence: low
Conditions are partial; exploit requires further evidence the analyzer did not produce.
Preconditions
- Application-specific invariant the analyzer flagged as possibly violated
Action
Operator review required to determine whether the flagged path is reachable and whether the impact materializes in this specific contract.
Impact
Depends on the specific invariant; impact assessment requires operator context.
False-positive caveats
- Logic flags are application-specific; the analyzer may have misread the intent.
- The flagged code path may be unreachable in production.
Remediation checklist
- Operator should manually validate the invariant the analyzer flagged.
- Add a unit test that exercises the suspected path.
- e71d79a6f3c49afd6c2f7ac29fb029ab8711b3280728ee65b2bd9cf38595ddf2 · uninitializedmediumConfidence: low
Conditions point at the exploit but at least one precondition needs operator confirmation.
Preconditions
- Storage variable used before being set in the constructor or initialize() function
- Upgradeable contract whose initialize() was not called
Action
Attacker calls initialize() (or relies on the default zero value) to set themselves as owner / admin.
Impact
Full takeover of the proxy or unbounded admin power.
False-positive caveats
- The contract may be deployed with the initializer invoked atomically by a factory.
- Default zero values may be intentional for the variable's semantics.
Remediation checklist
- Require initialize() to be called exactly once via OpenZeppelin Initializable.
- Disable initializers in the implementation constructor for upgradeable proxies.
- Add a deployment test that fails if initialize() is callable post-deployment.
- c2b2edf6cd116438bd83e93bf79908b5753d5a4c4954b9035f0028abfd4eeff7 · reentrancymediumConfidence: low
Conditions point at the exploit but at least one precondition needs operator confirmation.
Preconditions
- External call to an untrusted address before the contract's own state is updated
- Contract or callback path reachable from the external caller
- No nonReentrant guard or equivalent on the entry-point function
Action
Attacker contract receives control during the external call and re-enters the original function before the original state write completes, repeating the state-changing side effect.
Impact
Duplicated withdrawals, double-spend on accounting balances, or out-of-order updates to invariants the function relies on.
False-positive caveats
- The external call may be to a known, trusted contract whose behavior is provable.
- The function may be guarded indirectly by a flag or external lock not visible to the analyzer.
Remediation checklist
- Apply checks-effects-interactions: update internal state before any external call.
- Add a nonReentrant guard on the entry-point function.
- Where feasible, pull-payment instead of push-payment on user balances.
Audit pipeline
Audit cockpit
Honest stage-by-stage view of what VegaSec ran against this contract. Automated stages do not replace a human operator review.
Audit intake
Passed320ms replay12:37 AMNormalize the submitted contract target and confirm it can enter the Solidity audit lane.
Source acquisition
Passed1.4s replay12:37 AMResolve pasted source or verified explorer source without treating malformed input as demo data.
Toolchain validation
Partial2.3s replay12:37 AMConfirm the configured static analyzers can run and produce parseable output.
- One or more analyzers emitted warnings; report findings remain usable but should be read with limitations.
Static analysis
Partial84 findings8.8s replay12:37 AMRun static analyzers against the sandboxed source and collect raw detector evidence.
- One or more analyzers emitted warnings; report findings remain usable but should be read with limitations.
Finding normalization
Passed84 findings1.1s replay12:37 AMDedupe detectors, classify vulnerability classes and compute severity-weighted risk.
Exploitability review
Partial84 findings1.9s replay12:37 AMFrame automated findings with conservative exploitability and limitation notes.
- Automated exploitability review is conservative and does not replace a manual exploitability assessment.
Remediation draft
Partial84 findings1.5s replay12:37 AMPrepare remediation-oriented evidence for the shareable report artifact.
- Remediation notes are generated from detector evidence and require project-specific engineering review.
Operator review
Blocked0ms replay12:37 AMRecord whether a human operator artifact exists before buyer escalation.
- No operator review artifact is attached to this automated scan.
- Human operator review has not been attached to this automated scan yet.
Finalization
Partial84 findings620ms replay12:37 AMPublish the automated report artifact or explain why the scan failed closed.
Artifact: Automated Solidity report · solidity-2f746d702f766567
- Final report is an automated static-analysis artifact; no operator review artifact is attached.
How to read this report
Score, confidence, ranking: four moving parts, no hand-tuning.
Generated Oct 4, 2026, 12:37 AM · Solidity · Unitroller.sol
Score bands
0-19
AVOID-style triage · this report
Multiple high or critical findings, low source confidence, or unverified context. Public action should pause until a Private Review or a re-scan with better evidence.
20-49
High caution
Notable findings or thin evidence. Worth a Private Review before relying on the artifact.
50-69
Watch
Mixed signals: some evidence, some gaps. Re-scan after material changes to the target.
70-89
Clear surface (automated)
No critical or high findings via static analysis. Not a safety claim: human review is still recommended for diligence work.
90-100
Strong surface (automated)
No critical or high findings, verified source, and high source confidence. Not a safety claim: human review is still recommended for diligence work.
- Score
- Deterministic 0-100 derived from severity counts. Same formula across every report. Lower means more risk.
- Confidence
- Separate axis. Measures how much VegaSec trusts the input data. Low confidence pushes the verdict toward UNKNOWN; the two are never collapsed into one number.
- Ranking / percentile
- Only meaningful within the eligible Trust Index set. Shown on /trust-index when the eligible pool is large enough. Today the public index is a controlled preview.
Private Review is separate
A paid Private Review does not raise the public score on this report. Public score reflects public-source evidence only. Private Review adds operator attestation and a confidential memo, never a score bump.
Source provenance
Verified source via Etherscan
- Chain
- ETHEREUM
- Address
- 0x3d98…cd3b
- Contract name
- Unitroller
- Compiler
- v0.5.8+commit.23d335f2
- License
- -
- EVM version
- Default
- Optimization
- On · 200 runs
- File count
- 1
- Proxy implementation
- 0xbafe…b526
Provenance is the public-explorer metadata captured at scan time. It is not a re-verification of compilation; the analyzer ran against the source string as returned by the explorer.