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.