narayanayv (Community Member) asked a question.

Inclusion of Functionality from Untrusted Control Sphere (CWE ID 829)

Hi team, I am new to veracode, can you please guide me how can we resolve the above the above flaw.


VCode likes this.
  • vnhin (Veracode, Inc.)

    Hi @narayanayv (Community Member)​ ,

     

    The remediation for CWE 829 is going to vary a bit based on your implementation. It would help us to determine the correct approach you should take if we had a bit more context about your application and the details around the flaw that was reported. I would recommend you schedule a consultation call to discuss this in more detail with a member of my team. You can check out this knowledge article (https://community.veracode.com/s/article/How-to-schedule-a-consultation-call) on how to schedule a consultation call with us.

     

    Thanks,

    Veasna Nhin

    Senior Application Security Consultant

    Expand Post
  • narayanayv (Community Member)

    Hi,

    You can find below my app scan results below, and please respond if any fix for this.

     

    829

  • DMangal (Community Member)

    I am getting the exact same flaw as above screenshot.

    Anybody has any idea how to fix this?

  • vnhin (Veracode, Inc.)

    @narayanayv (Community Member)​ ,

     

    Your screenshot does provide a bit more context around your initial question about CWE 829, however, it doesn't provide the complete picture. I assume your screenshot is in reference to a PDF report which only provide high level information about the CWE category and not specific details about the flaw. I recommend reviewing the flaw in Triage Flaws for your application scan to get a better understand what actually is being flagged.

     

    Typically CWE 829 flaws found in dynamic scans are due to lack of a Content Security Policy (CSP). Lack of CSP in itself isn't a security risk but using a strict CSP provides additional protection against certain type of attacks (https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) . You can verify within the response header of your application whether CSP is used or not.

     

    A couple CSP directive in particular that we advise on setting is the default-src and script-src . These will ensure that you're only allowing JavaScript that you have defined and trust. Other CSP directive like frame-ancestors might also be useful to set to prevent click-jacking and not allowing your site to be framed. Keep in mind that some browser don't support CSP or certain CSP directives. You'll need to make sure the CSP directives you're specifying will work correctly for your application.

     

    Again, I would recommend you schedule a consultation call to discuss this in more detail with a member of my team. We can discuss the specifics around the flaw found in your application and what the appropriate approach would be to remediate. You can check out this knowledge article (https://community.veracode.com/s/article/How-to-schedule-a-consultation-call) on how to schedule a consultation call with us.

     

    Thanks,

    Veasna Nhin

    Senior Application Security Consultant

    Expand Post
    • narayanayv (Community Member)

      Hi @vnhin (Veracode, Inc.)​ ,

      Thanks for giving the information above, can you please help me where we can setup the CSP in webserver or else can you provide any reference link for CSP setup in webserver.

       

      Thanks,

      narayanayv.

      Expand Post

Topics (1)

No articles found
Loading

Ask the Community

Get answers, share a use case, discuss your favorite features, or get input from the community.