eslint-community/eslint-plugin-security

A more relevant "detect-object-injection"

Open

#21 建立於 2017年8月30日

在 GitHub 查看
 (20 留言) (12 反應) (0 負責人)JavaScript (2,074 star) (131 fork)batch import
help wanted

描述

Is there any way that we can work towards a more helpful/relevant report of Object injection sinks?

I can't think of a relevant security use case where Object injection would be relevant outside of the scope of a function directly linked to a web service.

I can understand based on tree traversal that determining the difference in between functions that are used in response to direct network calls would be [near] impossible to determine, but if I use bracket notation at the top level of my module, likely this rule should not notify.

貢獻者指南

技術棧
javascriptnodejs
領域
backendsecurity
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Node.js and JavaScriptESLint plugin developmentObject injection security concept
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Investigate the current implementation of the 'detect object injection' rule in the plugin. Review the comments in the issue for proposed approaches to reduce false positives. Consider adding a configuration option to limit the rule to functions directly handling network requests. See relevant files in the rules directory and existing test cases to understand the pattern detection logic.