Omniscia Euler Finance Audit
Chainlink Support Security Audit
Audit Overview
We were tasked with performing an audit of the Euler codebase and in particular the newly introduced code of the contracts in scope in relation to Chainlink support being introduced to the system.
Over the course of the audit, we identified certain assumptions that can currently be broken and should be prevented from being done so as well as an overall insecure Chainlink integration in relation to the latest answer function.
We advise the Euler Finance team to closely evaluate all minor-and-above findings identified in the report and promptly remediate them as well as consider all optimizational exhibits identified in the report.
Post-Audit Conclusion
The Euler Finance team provided extensive response documentation as well as GitHub commits that either remediated the issues identified on the report or deliberated them as some required extensive discussions.
After exchanging ideas back and forth with the Euler Finance team, we concluded that certain exhibits merited nullification and have proceeded to mark them as such. Overall, all exhibits have been adeqautely addressed by the Euler Finance team.
Contracts Assessed
Audit Synopsis
| Severity | Identified | Alleviated | Partially Alleviated | Acknowledged |
|---|---|---|---|---|
 | 0 | 0 | 0 | 0 |
 | 2 | 2 | 0 | 0 |
 | 4 | 4 | 0 | 0 |
 | 1 | 0 | 0 | 1 |
 | 1 | 1 | 0 | 0 |
During the audit, we filtered and validated a total of 2 findings utilizing static analysis tools as well as identified a total of 6 findings during the manual review of the codebase. We strongly recommend that any minor severity or higher findings are dealt with promptly prior to the project's launch as they introduce potential misbehaviours of the system as well as exploits.
The list below covers each segment of the audit in depth and links to the respective chapter of the report: