CVE-2022-0722
Public on
Last Modified:
Description
A flaw was found in the parse-url package. Affected versions of this package are vulnerable to information exposure due to an improper validation issue.
Additional Information
- This content is not included.Bugzilla 2103584: parse-url: Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository ionicabizau/parse-url
- Content from cwe.mitre.org is not included.CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer
- FAQ: Frequently asked questions about CVE-2022-0722
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.
External References
Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2022-0722
Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2022-0722
Affected Packages and Issued Red Hat Security Errata
| Products / Services | Components | State | Errata |
|---|---|---|---|
| RHPAM 7.13.1 async | parse-url | Fixed | RHSA-2022:6813 |
| Red Hat Integration Camel K 1 | parse-url | Will not fix | |
| Red Hat Integration Data Virtualisation Operator | parse-url | Out of support scope | |
| Red Hat Integration Service Registry | parse-url | Out of support scope | |
| Red Hat OpenShift Container Platform 4 | openshift4/ose-console | Not affected | |
| Red Hat OpenShift Dev Spaces | devspaces/dashboard-rhel8 | Not affected | |
| Red Hat OpenShift GitOps | openshift-gitops-1/argocd-rhel8 | Will not fix | |
| Red Hat OpenShift GitOps | openshift-gitops-1/console-plugin-rhel8 | Will not fix | |
| Red Hat OpenShift distributed tracing 2 | rhosdt/jaeger-all-in-one-rhel8 | Not affected | |
| Red Hat OpenShift distributed tracing 2 | rhosdt/jaeger-query-rhel8 | Not affected | |
| Red Hat OpenShift distributed tracing 2 | rhosdt/jaeger-agent-rhel8 | Will not fix | |
| Red Hat OpenShift distributed tracing 2 | rhosdt/jaeger-collector-rhel8 | Will not fix | |
| Red Hat OpenShift distributed tracing 2 | rhosdt/jaeger-es-index-cleaner-rhel8 | Will not fix | |
| Red Hat OpenShift distributed tracing 2 | rhosdt/jaeger-es-rollover-rhel8 | Will not fix | |
| Red Hat OpenShift distributed tracing 2 | rhosdt/jaeger-ingester-rhel8 | Will not fix | |
| Red Hat Quay 3 | quay/quay-rhel8 | Will not fix | |
| Red Hat build of Apicurio Registry 2 | parse-url | Affected |
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).
| CVSS v3 Score Breakdown | Red Hat | NVD |
|---|---|---|
| CVSS v3 Base Score | 7.5 | 7.5 |
| Attack Vector | Network | Network |
| Attack Complexity | Low | Low |
| Privileges Required | None | None |
| User Interaction | None | None |
| Scope | Unchanged | Unchanged |
| Confidentiality Impact | High | High |
| Integrity Impact | None | None |
| Availability Impact | None | None |
CVSS v3 Vector
Red Hat CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
For more information, see https://access.redhat.com/solutions/762393.
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
- "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
- "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.
What can I do if my product is listed as "Will not fix"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
What can I do if my product is listed as "Fix deferred"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
- Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
My product is listed as "Out of Support Scope". What does this mean?
Not sure what something means? Check out our Security Glossary.