Carbon: Got some security issues after scaned by AppScan on Cloud

Created on 10 Oct 2019  路  2Comments  路  Source: carbon-design-system/carbon

What package(s) are you using?

  • [x] carbon-components
  • [ ] carbon-components-react

Detailed description

Describe in detail the issue you're having.
We used ASoC to scan open source libs we are packaging in our product, some security issues reported by ASoC.
main issues reported:

  • Insecure Use of setAttribute
    鍥剧墖
  • Insecure HTTP Communication
    鍥剧墖
  • Query Insecure Manipulation of Child Node
    鍥剧墖
  • Insecure random number
    鍥剧墖

Is this issue related to a specific component?
No.
What did you expect to happen? What happened instead? What would you like to
see changed?
No security issue reported by ASoC because we package carbon in our product.
What browser are you working in?
N/A
What version of the Carbon Design System are you using?
10.6
What offering/product do you work on? Any pressing ship or release dates we
should be aware of?
IBM Service Management Unite

Steps to reproduce the issue

  1. Login ASoC: https://cloud.appscan.com
  2. Upload source code
  3. Scan
  4. Download report

Please create a reduced test case in CodeSandbox

Additional information

  • Screenshots or code
  • Notes
bug 馃悰

Most helpful comment

Had a chat with @Bin-Xiong yesterday, we saw that none of them is directly affecting his team, but we agreed that we avoid Math.random() usage for pre-caution.

All 2 comments

Hi @Bin-Xiong thank you for making this issue! We are not able to independently verify this as the logging into ASoC seems to be broken. Is this a blocking issue for your team and could you provide more context about ASoC?

Had a chat with @Bin-Xiong yesterday, we saw that none of them is directly affecting his team, but we agreed that we avoid Math.random() usage for pre-caution.

Was this page helpful?
0 / 5 - 0 ratings