Marked potential security vulnerabilities
See original GitHub issueIssue Description
Deployment type
(select the type below by replacing the space with an x
)
- [] Cloud Foundry Application (cf push)
- Kubernetes, using a helm chart
- Docker, using docker compose
- Docker, single container deploying all components
- Other (please provide below)
Apparently updating Marked to the latest release ^0.3.9 fixes the XSS vulnerabilities.
Expected behaviour
Actual behaviour
Steps to reproduce the behavior
Log output covering before error and any error statements
Insert log here
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
10 Common Web Security Vulnerabilities - Toptal
Don't suffer through a security breach—take action before any problems arise. Master these 10 common web security vulnerabilities now.
Read more >Vulnerabilities, Exploits, and Threats at a Glance - Rapid7
A Security Vulnerability is a weakness, flaw, or error found within a security system that has the potential to be leveraged by a...
Read more >Known Exploited Vulnerabilities Catalog | CISA
Multiple vulnerabilities in the web services interface of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software ...
Read more >Potential Vulnerability - an overview | ScienceDirect Topics
3.2 Threat model. Threat modelling is the process used to analyse and assess any potential vulnerabilities that may undermine a systems security. The...
Read more >Marked Project Marked : CVE security vulnerabilities, versions ...
This page lists vulnerability statistics for all versions of Marked Project Marked. Vulnerability statistics provide a quick overview for security ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@hamzahamidi It is indeed in master, but as I said, running
npm install
should remove it.However, I’ve raised a PR that just removes that specific dependency from the package-lock.json
PR: https://github.com/SUSE/stratos-ui/pull/1433