Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MMT- 3831: MMT React Vulnerabilities July 2024 #1264

Closed
wants to merge 13 commits into from
Closed

Conversation

tle1989
Copy link
Contributor

@tle1989 tle1989 commented Jul 25, 2024

Overview

What is the feature?

MMT React Vulnerabilities Reported by Snyk (high & fixable) on July 18, 2024
CWE-1333: fast-xml-parser
CWE-1333: micromatch

https://app.snyk.io/org/esdis-cumulus-core-gibs-cmr-etc./project/74c1d039-9245-4c53-8786-e8cd1c1713d0

Screenshot 2024-07-25 at 9 27 18 AM Screenshot 2024-07-25 at 9 27 34 AM

What is the Solution?

Update fast-xml-parser to 4.4.1
Update micromatch to 4.0.6

Will fix these 2 vulnerabilities on this branch MMT-3831

What areas of the application does this impact?

Affect versions of fast-xml-parser, and micromatch packages are vulnerable to Regular Expression Denial of Service (ReDoS)

Testing

Reproduction steps

  • Environment for testing: React local Env

BEFORE THE FIX -->Currently there are 28 vul
On branch MMT-3390
Run npm audit

Screenshot 2024-08-05 at 1 59 42 PM

Note that dicer, request, tough-cookie, and elliptic vulnerabilities currently have no fix available

Screenshot 2024-07-25 at 9 49 29 AM

AFTER THE FIX
Pull branch MMT-3831
Run npm audit

Screenshot 2024-08-05 at 5 30 54 PM

No fix available for this one
GHSA-977x-g7h5-7qgw

Screenshot 2024-08-06 at 9 32 02 AM

We currently still have No fix available for dicer, request, tough-cookie vulnerabilities and elliptic; ONLY fast-xml-parser, micromatch to 4.0.6 are being fixed according to the AC of the ticket

Checklist

  • I have added automated tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • [x ] My changes generate no new warnings

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.60%. Comparing base (0c84be5) to head (0413a35).
Report is 5 commits behind head on MMT-3390.

Additional details and impacted files
@@            Coverage Diff            @@
##           MMT-3390    #1264   +/-   ##
=========================================
  Coverage     97.59%   97.60%           
=========================================
  Files           358      359    +1     
  Lines          5373     5383   +10     
  Branches       1113     1124   +11     
=========================================
+ Hits           5244     5254   +10     
  Misses          128      128           
  Partials          1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mandyparson
Copy link
Contributor

When I pull MMT-3831 I don't see any changes to the # of vulnerabilites? It's at 22 vulnerabilities (3 moderate, 19 high) before and 22 vulnerabilities (2 moderate, 20 high) after.

@tle1989
Copy link
Contributor Author

tle1989 commented Aug 6, 2024

When I pull MMT-3831 I don't see any changes to the # of vulnerabilites? It's at 22 vulnerabilities (3 moderate, 19 high) before and 22 vulnerabilities (2 moderate, 20 high) after.

These vulnerabilities are new after I created the PR; which are not part of the AC; I also just fixed those here too, except those are not fixable.

@mandyparson
Copy link
Contributor

mandyparson commented Aug 7, 2024

Can you explain why we can't fix the ones that say a fix is available? ie HeaderParser in dicer and Elliptic's EDDSA missing signature length check?

Because pathed versions is None

@tle1989 tle1989 closed this Aug 7, 2024
@tle1989 tle1989 deleted the MMT-3831 branch August 7, 2024 17:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants