ecosystem stringclasses 14 values | vuln_id stringlengths 10 19 | summary stringlengths 4 267 ⌀ | details stringlengths 9 13.5k | aliases stringlengths 17 144 ⌀ | modified_date stringdate 2010-05-27 05:47:00 2022-05-10 08:46:52 | published_date stringdate 2005-12-31 05:00:00 2022-05-10 08:46:50 | severity stringclasses 5 values | score float64 0 10 ⌀ | cwe_id stringclasses 988 values | refs stringlengths 30 17.7k ⌀ | introduced stringlengths 75 4.26k ⌀ |
|---|---|---|---|---|---|---|---|---|---|---|---|
Go | GHSA-8wrg-m8vm-5fvj | Authentication Bypass by Primary Weakness in github.com/kongchuanhujiao/server | ### Impact
Authentication Bypass by Primary Weakness (CWE-305)
Commit:
https://github.com/kongchuanhujiao/server/commit/9a125624f219e496bdf4b07b404816d5a309bdc1
ALL Users is impacted.
### Patches
Yes, PLEASE UPGRADE TO v1.3.21-beta.d0ffc0a6 | {'CVE-2021-21403'} | 2021-05-20T22:25:09Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-305'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21403', 'https://github.com/kongchuanhujiao/server/security/advisories/GHSA-8wrg-m8vm-5fvj', 'https://github.com/kongchuanhujiao/server/commit/9a125624f219e496bdf4b07b404816d5a309bdc1'} | null |
Go | GHSA-m36x-mgfh-8g78 | Subdomain Takeover in Interactsh server | A domain configured with interactsh server was vulnerable to subdomain takeover for specfic subdomain, i.e `app`, Interactsh server before `< 1.0.0` used to create cname entries for `app` pointing to `projectdiscovery.github.io` as default which intended to used for hosting interactsh [web client](https://github.com/projectdiscovery/interactsh-web) using GitHub pages. It turns out to be a security issue with a self-hosted interactsh server in which the user may not have configured a web client but still have a cname entry pointing to GitHub pages, making them vulnerable to subdomain takeover.
This issue was initially reported to us as a subdomain takeover for one of our domains that runs interactsh server by **Melih** at `security@projectdiscovery.io`, and after conducting an internal investigation, we determined that it was an issue with the default config of interactsh server affecting all the server running self-hosted instance of interactsh, as a result - cname entry has been removed in the latest release.
#### Impact
This allows one to host / run arbitrary client side code (XSS) in a user's browser when browsing the vulnerable subdomain, for more details on the impact, please read this [detailed blogpost](https://labs.detectify.com/2014/10/21/hostile-subdomain-takeover-using-herokugithubdesk-more/) from Detectify.
#### Patches
Update to [Interactsh server v1.0.0 ](https://github.com/projectdiscovery/interactsh/releases/tag/v1.0.0)with `go install -v github.com/projectdiscovery/interactsh/cmd/interactsh-server@latest`
#### References
https://github.com/projectdiscovery/interactsh/issues/136
#### For more information
If you have any questions or comments about this advisory:
* Email us at [security@projectdiscovery.io](mailto:security@projectdiscovery.io)
| null | 2022-01-24T22:24:55Z | 2022-01-27T15:15:25Z | HIGH | null | {'CWE-79'} | {'https://github.com/projectdiscovery/interactsh', 'https://github.com/projectdiscovery/interactsh/issues/136', 'https://github.com/projectdiscovery/interactsh/security/advisories/GHSA-m36x-mgfh-8g78'} | null |
Go | GHSA-mqf3-28j7-3mj6 | Information Exposure in Kubernetes | Kubernetes before 1.2.0-alpha.5 allows remote attackers to read arbitrary pod logs via a container name. | {'CVE-2015-7528'} | 2022-04-12T22:40:14Z | 2022-04-12T22:40:14Z | MODERATE | null | {'CWE-200'} | {'https://github.com/openshift/origin/pull/6113', 'http://rhn.redhat.com/errata/RHSA-2015-2615.html', 'https://nvd.nist.gov/vuln/detail/CVE-2015-7528', 'https://github.com/kubernetes/kubernetes/commit/afd56495a1052a3387b81df1786a8d0f51bc8671', 'https://github.com/kubernetes/kubernetes/pull/17886', 'https://github.com/kubernetes/kubernetes', 'https://github.com/kubernetes/kubernetes/releases/tag/v1.2.0-alpha.5', 'https://access.redhat.com/errata/RHSA-2015:2544'} | null |
Go | GO-2021-0075 | null | Due to improper argument validation in RPC messages, a maliciously crafted
message can cause a panic, leading to denial of service.
| {'CVE-2018-12018'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://peckshield.com/2018/06/27/EPoD/', 'https://github.com/ethereum/go-ethereum/commit/a5237a27eaf81946a3edb4fafe13ed6359d119e4', 'https://github.com/ethereum/go-ethereum/pull/16891'} | null |
Go | GHSA-rmw5-xpg9-jr29 | Use of Cryptographically Weak Pseudo-Random Number Generator in Rclone | An issue was discovered in Rclone before 1.53.3. Due to the use of a weak random number generator, the password generator has been producing weak passwords with much less entropy than advertised. The suggested passwords depend deterministically on the time the second rclone was started. This limits the entropy of the passwords enormously. These passwords are often used in the crypt backend for encryption of data. It would be possible to make a dictionary of all possible passwords with about 38 million entries per password length. This would make decryption of secret material possible with a plausible amount of effort. NOTE: all passwords generated by affected versions should be changed. | {'CVE-2020-28924'} | 2022-04-27T20:30:31Z | 2021-06-10T17:23:21Z | HIGH | null | {'CWE-331', 'CWE-338'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-28924', 'https://github.com/rclone/rclone', 'https://security.gentoo.org/glsa/202107-14', 'https://github.com/rclone/rclone/issues/4783', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UJIFT24Q6EFXLQZ24AER2QGFFZLMIPCD/'} | null |
Go | GHSA-6w7g-p4jh-rf92 | "Verify All" Returns Success Despite Validation Failures in Singularity | ### Impact
The `--all / -a` option to `singularity verify` returns success even when some objects in a SIF container are not signed, or cannot be verified.
The SIF objects that are not verified are reported in `WARNING` log messages, but a `Container Verified` message and exit code of `0` are returned.
Workflows that verify a container using `--all / -a` and use the exit code as an indicator of success are vulnerable to running SIF containers that have unsigned, or modified, objects that may be exploited to introduce malicious behavior.
```
$ singularity verify -a image.sif
WARNING: Missing signature for SIF descriptor 2 (JSON.Generic)
WARNING: Missing signature for SIF descriptor 3 (FS)
Container is signed by 1 key(s):
Verifying partition: Def.FILE:
12045C8C0B1004D058DE4BEDA20C27EE7FF7BA84
[LOCAL] Unit Test <unit@test.com>
[OK] Data integrity verified
INFO: Container verified: image.sif
$ echo $?
0
```
### Patches
Singularity 3.6.0 has a new implementation of sign/verify that fixes this issue.
All users are advised to upgrade to 3.6.0. Note that Singularity 3.6.0 uses a new signature format that is necessarily incompatible with Singularity < 3.6.0 - e.g. Singularity 3.5.3 cannot verify containers signed by 3.6.0.
Version 3.6.0 includes a `--legacy-insecure` flag for the `singularity verify` command, that will perform verification of the older, and insecure, legacy signatures for compatibility with existing containers. This does not guarantee that containers have not been modified since signing, due to other issues in the legacy signature format.
### Workarounds
If you are unable to update to 3.6.0 ensure that you do not rely on the return code of `singularity verify --all / -a` as an indicator of trust in a container.
Note that other issues in the sign/verify implementation in Singularity < 3.6.0 allow additional means to introduce malicious behavior to a signed container.
### For more information
General questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:
* [Singularity Slack Channel](https://bit.ly/2m0g3lX)
* [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)
Any sensitive security concerns should be directed to: security@sylabs.io
See our Security Policy here: https://sylabs.io/security-policy | {'CVE-2020-13846'} | 2021-10-05T17:17:55Z | 2021-12-20T18:24:43Z | HIGH | null | null | {'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00046.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00053.html', 'https://github.com/sylabs/singularity', 'https://github.com/hpcng/singularity/security/advisories/GHSA-6w7g-p4jh-rf92', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00059.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13846'} | null |
Go | GHSA-wqv3-8cm6-h6wg | Improper Authentication in Kubernetes | A security issue was discovered in kube-proxy which allows adjacent hosts to reach TCP and UDP services bound to 127.0.0.1 running on the node or in the node's network namespace. For example, if a cluster administrator runs a TCP service on a node that listens on 127.0.0.1:1234, because of this bug, that service would be potentially reachable by other hosts on the same LAN as the node, or by containers running on the same node as the service. If the example service on port 1234 required no additional authentication (because it assumed that only other localhost processes could reach it), then it could be vulnerable to attacks that make use of this bug.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8558
https://www.openwall.com/lists/oss-security/2020/07/08/1 | {'CVE-2020-8558'} | 2021-05-24T19:30:36Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-420', 'CWE-287'} | {'https://groups.google.com/g/kubernetes-announce/c/sI4KmlH3S2I/m/TljjxOBvBQAJ', 'https://bugzilla.redhat.com/show_bug.cgi?id=1843358', 'https://labs.bishopfox.com/tech-blog/bad-pods-kubernetes-pod-privilege-escalation', 'https://github.com/kubernetes/kubernetes/issues/92315', 'https://security.netapp.com/advisory/ntap-20200821-0001/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8558', 'https://github.com/tabbysable/POC-2020-8558', 'https://github.com/bottlerocket-os/bottlerocket/security/advisories/GHSA-wqv3-8cm6-h6wg', 'https://groups.google.com/g/kubernetes-security-announce/c/B1VegbBDMTE'} | null |
Go | GHSA-j9wf-vvm6-4r9w | Unverified Ownership in Kubernetes | Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.externalIPs field, to intercept traffic to that IP address. Additionally, an attacker who is able to patch the status (which is considered a privileged operation and should not typically be granted to users) of a LoadBalancer service can set the status.loadBalancer.ingress.ip to similar effect. | {'CVE-2020-8554'} | 2022-03-30T21:20:33Z | 2022-02-08T21:50:34Z | MODERATE | null | {'CWE-283', 'CWE-863'} | {'https://lists.apache.org/thread.html/r1975078e44d96f2a199aa90aa874b57a202eaf7f25f2fde6d1c44942@%3Ccommits.druid.apache.org%3E', 'https://groups.google.com/g/kubernetes-security-announce/c/iZWsF9nbKE8', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8554', 'https://lists.apache.org/thread.html/r0c76b3d0be348f788cd947054141de0229af00c540564711e828fd40@%3Ccommits.druid.apache.org%3E', 'https://github.com/kubernetes/kubernetes/issues/97076', 'https://github.com/kubernetes/kubernetes/issues/97110', 'https://github.com/kubernetes/kubernetes', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://www.oracle.com//security-alerts/cpujul2021.html', 'https://lists.apache.org/thread.html/rcafa485d63550657f068775801aeb706b7a07140a8ebbdef822b3bb3@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/rdb223e1b82e3d7d8e4eaddce8dd1ab87252e3935cc41c859f49767b6@%3Ccommits.druid.apache.org%3E'} | null |
Go | GHSA-gjcg-vrxg-xmgv | Incorrect handling of H2 GOAWAY + SETTINGS frames | Envoy, which Pomerium is based on, can abnormally terminate if an H/2 GOAWAY and SETTINGS frame are received in the same IO event.
### Impact
This can lead to a DoS in the presence of untrusted *upstream* servers.
### Patches
0.15.1 contains an upgraded envoy binary with this vulnerability patched.
### Workarounds
If only trusted upstreams are configured, there is not substantial risk of this condition being triggered.
### References
[envoy GSA](https://github.com/envoyproxy/envoy/security/advisories/GHSA-j374-mjrw-vvp8)
[envoy CVE](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32780)
[envoy announcement](https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [pomerium/pomerium](https://github.com/pomerium/pomerium/issues)
* Email us at [security@pomerium.com](mailto:security@pomerium.com)
| {'CVE-2021-39162'} | 2021-09-10T16:32:16Z | 2021-09-10T17:54:01Z | HIGH | null | {'CWE-754'} | {'https://github.com/pomerium/pomerium/security/advisories/GHSA-gjcg-vrxg-xmgv', 'https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ', 'https://github.com/envoyproxy/envoy/security/advisories/GHSA-j374-mjrw-vvp8', 'https://github.com/pomerium/pomerium', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39162'} | null |
Go | GHSA-pf59-j7c2-rh6x | Exposure of Sensitive Information to an Unauthorized Actor and Insertion of Sensitive Information Into Sent Data in Calico | Clusters using Calico (version 3.14.0 and below), Calico Enterprise (version 2.8.2 and below), may be vulnerable to information disclosure if IPv6 is enabled but unused. A compromised pod with sufficient privilege is able to reconfigure the node’s IPv6 interface due to the node accepting route advertisement by default, allowing the attacker to redirect full or partial network traffic from the node to the compromised pod. | {'CVE-2020-13597'} | 2021-05-14T16:27:14Z | 2022-02-15T01:57:18Z | LOW | null | {'CWE-200', 'CWE-201'} | {'https://www.projectcalico.org/security-bulletins/', 'https://github.com/containernetworking/plugins/pull/484/', 'https://github.com/kubernetes/kubernetes/issues/91507', 'https://groups.google.com/forum/#!topic/kubernetes-security-announce/BMb_6ICCfp8', 'https://github.com/containernetworking/plugins/commit/ad10b6fa91aacd720f1f9ab94341a97a82a24965', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13597'} | null |
Go | GO-2020-0045 | null | CSRF tokens are generated using math/rand, which is not a cryptographically secure
rander number generation, making predicting their values relatively trivial and
allowing an attacker to bypass CSRF protections which relatively few requests.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/dinever/golf/commit/3776f338be48b5bc5e8cf9faff7851fc52a3f1fe', 'https://github.com/dinever/golf/issues/20', 'https://github.com/dinever/golf/pull/24'} | null |
Go | GO-2021-0059 | null | Due to improper bounds checking, maliciously crafted JSON objects
can cause an out-of-bounds panic. If parsing user input, this may
be used as a denial of service vector.
| {'CVE-2020-35380'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/tidwall/gjson/issues/192', 'https://github.com/tidwall/gjson/commit/f0ee9ebde4b619767ae4ac03e8e42addb530f6bc'} | null |
Go | GHSA-g2qx-6ghw-67hm | Denial of Service in Gitea | An issue was discovered in Gitea in which an attacker can trigger a deadlock by initiating a transfer of a repository's ownership from one organization to another. | {'CVE-2020-13246'} | 2021-05-20T22:20:34Z | 2022-02-15T00:33:30Z | HIGH | null | {'CWE-667'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-13246', 'https://github.com/go-gitea/gitea/pull/11438', 'https://github.com/go-gitea/gitea/issues/10549', 'https://www.youtube.com/watch?v=DmVgADSVS88'} | null |
Go | GHSA-rfq3-w54c-f9q5 | OAuth2 Redirect URL validity does not respect query parameters and character casing for loopback addresses | ### Impact
[fosite#400](https://github.com/ory/fosite/pull/400) (released as v0.30.2) introduced a new feature for handling redirect URLs pointing to loopback interfaces ([rfc8252#section-7.3](https://tools.ietf.org/html/rfc8252#section-7.3)). As part of that change new behavior was introduced which failed to respect the redirect URL's (only for loopback interfaces!) query parameters
1. Registering a client with allowed redirect URL `http://127.0.0.1/callback`
2. Performing OAuth2 flow and requesting redirect URL `http://127.0.0.1/callback?bar=foo`
3. Instead of an error, the browser is redirected to `http://127.0.0.1/callback?bar=foo` with a potentially successful OAuth2 response.
as well as the host parameter (as long as the host is a loopback interface):
1. Registering a client with allowed redirect URL `https://example.com/callback`
2. Performing OAuth2 flow and requesting redirect URL `http://127.0.0.1/callback`
3. Instead of an error, the browser is redirected to `http://127.0.0.1/callback` with a potentially successful OAuth2 response.
These bugs are only applicable in scenarios where the attacker has control over the loopback interface (`localhost`, `127.0.0.1`, `[::1]`) where the browser performing the OAuth2 flow is running. | {'CVE-2020-15233'} | 2021-11-19T14:42:56Z | 2021-05-24T17:00:12Z | MODERATE | null | {'CWE-601', 'CWE-20'} | {'https://github.com/ory/fosite', 'https://github.com/ory/fosite/security/advisories/GHSA-rfq3-w54c-f9q5', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15233', 'https://github.com/ory/fosite/pull/400', 'https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf'} | null |
Go | GHSA-rqjq-mrgx-85hp | Allocation of Resources Without Limits or Throttling in Hashicorp Consul | HashiCorp Consul and Consul Enterprise include an HTTP API (introduced in 1.2.0) and DNS (introduced in 1.4.3) caching feature that was vulnerable to denial of service. Fixed in 1.6.6 and 1.7.4. | {'CVE-2020-13250'} | 2021-07-29T18:19:34Z | 2021-05-18T18:21:35Z | HIGH | null | {'CWE-770'} | {'https://github.com/hashicorp/consul/blob/v1.6.6/CHANGELOG.md', 'https://github.com/hashicorp/consul/commit/72f92ae7ca4cabc1dc3069362a9b64ef46941432', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13250', 'https://github.com/hashicorp/consul/pull/8023', 'https://github.com/hashicorp/consul/blob/v1.7.4/CHANGELOG.md'} | null |
Go | GO-2020-0012 | null | An attacker can craft an ssh-ed25519 or sk-ssh-ed25519@openssh.com public
key, such that the library will panic when trying to verify a signature
with it. If verifying signatures using user supplied public keys, this
may be used as a denial of service vector.
| {'CVE-2020-9283'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://go-review.googlesource.com/c/crypto/+/220357', 'https://github.com/golang/crypto/commit/bac4c82f69751a6dd76e702d54b3ceb88adab236', 'https://groups.google.com/g/golang-announce/c/3L45YRc91SY'} | null |
Go | GHSA-ch68-7cf4-35vr | Limited ability to spoof SAML authentication with missing audience verification in Fleet | ### Impact
This impacts deployments using SAML SSO in two specific cases:
1. A malicious or compromised Service Provider (SP) could reuse the SAML response to log into Fleet as a user -- only if the user has an account with the same email in Fleet, _and_ the user signs into the malicious SP via SAML SSO from the same Identity Provider (IdP) configured with Fleet.
2. A user with an account in Fleet could reuse a SAML response intended for another SP to log into Fleet. This is only a concern if the user is blocked from Fleet in the IdP, but continues to have an account in Fleet. If the user is blocked from the IdP entirely, this cannot be exploited.
### Patches
Fleet 4.9.1 resolves this issue.
### Workarounds and good practices
* Reduce the length of sessions on your IdP to reduce the window for malicious re-use.
* Limit the amount of SAML Service Providers/Applications used by user accounts with access to Fleet.
* When removing access to Fleet in the IdP, delete the Fleet user from Fleet as well.
### For more information
If you have any questions or comments about this advisory:
* Join us in the #fleet channel of [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw).
* Email us at [security@fleetdm.com](mailto:security@fleetdm.com). | {'CVE-2022-23600'} | 2022-02-07T21:57:38Z | 2022-02-07T21:57:38Z | MODERATE | null | {'CWE-287', 'CWE-284'} | {'https://github.com/fleetdm/fleet', 'https://github.com/fleetdm/fleet/commit/35d5a7b285f15ddd47486fa656e8b1acf3d48374', 'https://github.com/fleetdm/fleet/security/advisories/GHSA-ch68-7cf4-35vr', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23600'} | null |
Go | GHSA-rffr-c932-cpxv | Cross-site Request Forgery (CSRF) in Cloud Native Computing Foundation Harbor | Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows CSRF in the VMware Harbor Container Registry for the Pivotal Platform. | {'CVE-2019-19025'} | 2021-05-04T22:01:58Z | 2021-05-18T18:27:50Z | MODERATE | null | {'CWE-352'} | {'https://github.com/goharbor/harbor/security/advisories/GHSA-gcqm-v682-ccw6', 'https://github.com/goharbor/harbor/security/advisories', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19025', 'https://tanzu.vmware.com/security/cve-2019-19025'} | null |
Go | GHSA-2v6x-frw8-7r7f | Exposure of Sensitive Information to an Unauthorized Actor in kube-state-metrics | A security issue was discovered in kube-state-metrics 1.7.x before 1.7.2. An experimental feature was added to v1.7.0 and v1.7.1 that enabled annotations to be exposed as metrics. By default, kube-state-metrics metrics only expose metadata about Secrets. However, a combination of the default kubectl behavior and this new feature can cause the entire secret content to end up in metric labels, thus inadvertently exposing the secret content in metrics. | {'CVE-2019-17110'} | 2021-05-17T21:04:15Z | 2021-05-18T15:38:54Z | MODERATE | null | {'CWE-200'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-17110', 'https://github.com/kubernetes/kube-state-metrics/commit/2a9ab3a9a0f1c4dbecb6a5577185b33bfac86a96', 'https://github.com/kubernetes/kube-state-metrics/releases/tag/v1.7.2', 'https://github.com/kubernetes/kube-state-metrics/commit/03122fe3e2df49a9a7298b8af921d3c37c430f7f'} | null |
Go | GO-2020-0004 | null | If any of the `ListenAndServe` functions are called with an empty token,
token authentication is disabled globally for all listeners.
Also, a minor timing side channel was present allowing attackers with
very low latency and able to make a lot of requests to potentially
recover the token.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/nanobox-io/golang-nanoauth/pull/5', 'https://github.com/nanobox-io/golang-nanoauth/commit/063a3fb69896acf985759f0fe3851f15973993f3'} | null |
Go | GHSA-q8q8-93cv-v6h8 | Lookup function information discolosure in helm | The Helm core maintainers have identified an information disclosure vulnerability in Helm 3.0.0-3.1.2.
### Impact
`lookup` is a Helm template function introduced in Helm v3. It is able to lookup resources in the cluster to check for the existence of specific resources and get details about them. This can be used as part of the process to render templates.
The documented behavior of `helm template` states that it does not attach to a remote cluster. However, as the recently added `lookup` template function circumvents this restriction and connects to the cluster even during `helm template` and `helm install|update|delete|rollback --dry-run`. The user is not notified of this behavior.
Running `helm template` should not make calls to a cluster. This is different from `install`, which is presumed to have access to a cluster in order to load resources into Kubernetes. Helm 2 is unaffected by this vulnerability.
A malicious chart author could inject a `lookup` into a chart that, when rendered through `helm template`, performs unannounced lookups against the cluster a user's `KUBECONFIG` file points to. This information can then be disclosed via the output of `helm template`.
### Patches
This issue has been fixed in Helm 3.2.0
### Workarounds
Due to another bug (also fixed in Helm 3.2.0), the command `helm lint` will fail with an error if the `lookup` function is used in a chart. Therefore, run `helm lint` on an untrusted chart before running `helm template`.
Alternately, setting the `KUBECONFIG` environment variable to point to an empty Kubernetes configuration file will prevent unintended network connections.
Finally, a chart may be manually analyzed for the presence of a `lookup` function in any file in the `templates/` directory.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the Helm repository](https://github.com/helm/helm/issues)
* For security-specific issues, email us at [cncf-helm-security@lists.cncf.io](mailto:cncf-helm-security@lists.cncf.io) | {'CVE-2020-11013'} | 2021-05-24T21:15:16Z | 2021-05-27T18:44:56Z | HIGH | null | {'CWE-200'} | {'https://github.com/helm/helm/security/advisories/GHSA-q8q8-93cv-v6h8', 'https://github.com/helm/helm/pull/7969', 'https://github.com/helm/helm/releases/tag/v3.2.0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11013', 'https://github.com/helm/helm/pull/7969/commits/c67b644a791a8fa61c760a3a0474533e63e74008'} | null |
Go | GHSA-wp47-9r3h-xfgq | Server-Side Request Forgery in Apache Traffic Control | In Apache Traffic Control Traffic Ops prior to 6.1.0 or 5.1.6, an unprivileged user who can reach Traffic Ops over HTTPS can send a specially-crafted POST request to /user/login/oauth to scan a port of a server that Traffic Ops can reach. | {'CVE-2022-23206'} | 2022-02-14T22:58:25Z | 2022-02-07T00:00:23Z | HIGH | null | {'CWE-918'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-23206', 'https://lists.apache.org/thread/lsrd2mqj29vrvwsh8g0d560vvz8n126f'} | null |
Go | GHSA-c8xp-8mf3-62h9 | OctoRPKI lacks contextual out-of-bounds check when validating RPKI ROA maxLength values | Any CA issuer in the RPKI can trick OctoRPKI prior to https://github.com/cloudflare/cfrpki/commit/a8db4e009ef217484598ba1fd1c595b54e0f6422 into emitting an invalid VRP "MaxLength" value, causing RTR sessions to terminate.
### Impact
An attacker can use this to disable RPKI Origin Validation in a victim network (for example AS 13335 - Cloudflare) prior to launching a BGP hijack which during normal operations would be rejected as "RPKI invalid". Additionally, in certain deployments RTR session flapping in and of itself also could cause BGP routing churn, causing availability issues.
### Patches
https://github.com/cloudflare/cfrpki/commit/a8db4e009ef217484598ba1fd1c595b54e0f6422
https://github.com/cloudflare/cfrpki/releases/tag/v1.3.0
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@cloudflare.com](security@cloudflare.com)
| {'CVE-2021-3761'} | 2021-09-03T21:40:39Z | 2021-09-07T23:02:18Z | HIGH | null | {'CWE-787', 'CWE-295'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3761', 'https://www.debian.org/security/2022/dsa-5041', 'https://github.com/cloudflare/cfrpki/commit/a8db4e009ef217484598ba1fd1c595b54e0f6422', 'https://github.com/cloudflare/cfrpki/releases/tag/v1.3.0', 'github.com/cloudflare/cfrpki', 'https://github.com/cloudflare/cfrpki/security/advisories/GHSA-c8xp-8mf3-62h9'} | null |
Go | GHSA-86f3-hf24-76q4 | Use of Hard-coded Cryptographic Key in Netmaker | ### Impact
There is a hard-coded cryptographic key in the code base which can be exploited to run admin commands on a remote server, if you know the address and username of the admin. This effects the server (netmaker) component, and not clients.
### Patches
This has been patched in Netmaker v0.8.5, v0.9.4, and v0.10.0. If you are running these versions, the fix is to perform the following:
1. docker-compose down
2. docker pull gravitl/netmaker:( version )
3. docker-compose up -d
#### Additional Information
If you are running **any other version**, you will need to upgrade to one of these three versions. If you have a special circumstance that requires running a different version, let us know and we may be able to build a custom patch.
### For more information
If you have any questions or comments about this advisory:
* Email us at [info@gravitl.com](mailto:info@gravitl.com)
| {'CVE-2022-23650'} | 2022-02-22T19:40:23Z | 2022-02-22T19:40:23Z | HIGH | null | {'CWE-321', 'CWE-798'} | {'https://github.com/gravitl/netmaker/commit/e9bce264719f88c30e252ecc754d08f422f4c080', 'https://github.com/gravitl/netmaker/security/advisories/GHSA-86f3-hf24-76q4', 'https://github.com/gravitl/netmaker/commit/3d4f44ecfe8be4ca38920556ba3b90502ffb4fee', 'https://github.com/gravitl/netmaker/pull/781/commits/1bec97c662670dfdab804343fc42ae4b1d050a87', 'https://github.com/gravitl/netmaker', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23650'} | null |
Go | GHSA-99cg-575x-774p | Improper Input Validation in AKPublic.Verify with attacker-controlled TPM Quote | ### Impact
An improper input validation vulnerability in go-attestation before 0.4.0 allows local users to provide a maliciously-formed Quote over no/some PCRs, causing `AKPublic.Verify` to succeed despite the inconsistency. Subsequent use of the same set of PCR values in `Eventlog.Verify` lacks the authentication performed by quote verification, meaning a local attacker could couple this vulnerability with a maliciously-crafted TCG log in `Eventlog.Verify` to spoof events in the TCG log, hence defeating remotely-attested measured-boot.
### Patches
This issue is resolved in version 0.4.0. If your usage of this library verifies PCRs using multiple quotes, make sure to use the new method `AKPublic.VerifyAll()` instead of `AKPublic.Verify`. | {'CVE-2022-0317'} | 2022-02-11T15:06:33Z | 2022-02-01T00:43:17Z | MODERATE | null | {'CWE-20'} | {'https://github.com/google/go-attestation/security/advisories/GHSA-99cg-575x-774p', 'https://github.com/google/go-attestation/commit/82f2c9c2c76e1d3691d17ee78116d1d93a123788', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0317', 'https://github.com/google/go-attestation/'} | null |
Go | GHSA-gwj5-3vfq-q992 | Import loops in account imports, nats-server DoS | (This advisory is canonically <https://advisories.nats.io/CVE/CVE-2020-28466.txt>)
## Problem Description
An export/import cycle between accounts could crash the nats-server, after consuming CPU and memory.
This issue was fixed publicly in <https://github.com/nats-io/nats-server/pull/1731> in November 2020.
The need to call this out as a security issue was highlighted by `snyk.io` and we are grateful for their assistance in doing so.
Organizations which run a NATS service providing access to accounts run by untrusted third parties are affected.
See below for an important caveat if running such a service.
## Affected versions
#### NATS Server
* Version 2 prior to 2.2.0
+ 2.0.0 through and including 2.1.9 are vulnerable.
* fixed with nats-io/nats-server PR 1731, commit 2e3c226729
## Impact
The nats-server could be killed, after consuming resources.
## Workaround
The import cycle requires at least two accounts to work; if you have open account sign-up, then restricting new account sign-up might hinder an attacker.
## Solution
Upgrade the nats-server.
## Caveat on NATS with untrusted users
Running a NATS service which is exposed to untrusted users presents a heightened risk.
Any remote execution flaw or equivalent seriousness, or denial-of-service by unauthenticated users, will lead to prompt releases by the NATS maintainers.
Fixes for denial of service issues with no threat of remote execution, when limited to account holders, are likely to just be committed to the main development branch with no special attention.
Those who are running such services are encouraged to build regularly from git. | null | 2021-05-20T21:07:16Z | 2021-05-21T16:22:16Z | LOW | null | {'CWE-400'} | {'https://github.com/nats-io/nats-server/security/advisories/GHSA-gwj5-3vfq-q992'} | null |
Go | GHSA-pw59-4qgf-jxr8 | Cache Manipulation Attack in Apache Traffic Control | When ORT (now via atstccfg) generates ip_allow.config files in Apache Traffic Control 3.0.0 to 3.1.0 and 4.0.0 to 4.1.0, those files include permissions that allow bad actors to push arbitrary content into and remove arbitrary content from CDN cache servers. Additionally, these permissions are potentially extended to IP addresses outside the desired range, resulting in them being granted to clients possibly outside the CDN arcitechture. | {'CVE-2020-17522'} | 2022-04-04T21:27:42Z | 2021-06-18T22:04:32Z | MODERATE | null | {'CWE-525', 'CWE-732'} | {'https://github.com/apache/trafficcontrol/commit/492290d810e9608afb5d265b98cd3f3e153e776b', 'https://github.com/apache/trafficcontrol', 'https://lists.apache.org/thread.html/rc8bfd7d4f71d61e9193efcd4699eccbab3c202ec1d75ed9d502f08bf@%3Ccommits.trafficcontrol.apache.org%3E', 'https://lists.apache.org/thread.html/r3c675031ac220b5eae64a9c84a03ee60045c6045738607dca4a96cb8@%3Ccommits.trafficcontrol.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-17522', 'https://lists.apache.org/thread.html/r3de212a3da73bcf98fa2db7eafb75b2eb8e131ff466e6efc4284df09%40%3Cdev.trafficcontrol.apache.org%3E'} | null |
Go | GHSA-h3q4-vmw4-cpr5 | Path Traversal in Gitea | The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL. | {'CVE-2021-29134'} | 2022-03-28T22:26:45Z | 2022-03-16T00:00:38Z | MODERATE | null | {'CWE-22'} | {'https://github.com/go-gitea/gitea/releases/tag/v1.13.6', 'https://github.com/go-gitea/gitea/releases', 'https://github.com/go-gitea/gitea/pull/15125/files', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29134', 'https://github.com/go-gitea/gitea'} | null |
Go | GHSA-82mm-ffjr-h86c | Authorization bypass in Istio | "In Istio 1.5.0 though 1.5.8 and Istio 1.6.0 through 1.6.7, when users specify an AuthorizationPolicy resource with DENY actions using wildcard suffixes (e.g. *-some-suffix) for source principals or namespace fields, callers will never be denied access, bypassing the intended policy." | {'CVE-2020-16844'} | 2021-05-12T21:59:07Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-284'} | {'https://github.com/istio/istio/releases/tag/1.5.9', 'https://istio.io/latest/news/releases/1.5.x/announcing-1.5.9/', 'https://github.com/istio/istio/releases', 'https://istio.io/latest/news/releases/1.6.x/announcing-1.6.8/', 'https://github.com/istio/istio/commit/72d2e135374f421b656d6f1a21f474db46134ace', 'https://istio.io/latest/news/security/istio-security-2020-009/', 'https://github.com/istio/istio/releases/tag/1.6.8', 'https://github.com/istio/istio/commit/4c73414556b83f0e75c1b3a0a89a23103a71573c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-16844'} | null |
Go | GO-2020-0024 | null | The RemoteAddr and LocalAddr methods on the returned net.Conn may
call themselves, leading to an infinite loop which will crash the
program due to a stack overflow.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/btcsuite/go-socks/commit/233bccbb1abe02f05750f7ace66f5bffdb13defc'} | null |
Go | GHSA-w73w-5m7g-f7qc | Authorization bypass in github.com/dgrijalva/jwt-go | jwt-go allows attackers to bypass intended access restrictions in situations with []string{} for m["aud"] (which is allowed by the specification). Because the type assertion fails, "" is the value of aud. This is a security problem if the JWT token is presented to a service that lacks its own audience check. There is no patch available and users of jwt-go are advised to migrate to [golang-jwt](https://github.com/golang-jwt/jwt) at version 3.2.1 | {'CVE-2020-26160'} | 2021-06-28T21:32:34Z | 2021-05-18T21:08:21Z | HIGH | null | {'CWE-287', 'CWE-755'} | {'https://github.com/dgrijalva/jwt-go/issues/422', 'https://github.com/dgrijalva/jwt-go/pull/426', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515', 'https://github.com/dgrijalva/jwt-go/issues/462', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26160'} | null |
Go | GHSA-93p5-8fqw-wjx3 | Authentication bypass by capture-replay in github.com/cosmos/ethermint | Cosmos Network Ethermint <= v0.4.0 is affected by a transaction replay vulnerability in the EVM module. If the victim sends a very large nonce transaction, the attacker can replay the transaction through the application. | {'CVE-2021-25834'} | 2021-05-12T21:17:36Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-294', 'CWE-287'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-25834', 'https://github.com/cosmos/ethermint/commit/d7bdbd7488644f0aaeee5cdcdc119c863f199f72', 'https://github.com/cosmos/ethermint/releases/tag/v0.4.1', 'https://github.com/cosmos/ethermint/issues/686'} | null |
Go | GHSA-6jm6-cmcp-fqjq | Nomad Spread Job Stanza May Trigger Panic in Servers | Nomad and Nomad Enterprise allows operators with job-submit capabilities to use the spread stanza in a way such that it can cause panic in Nomad servers. This vulnerability, CVE-2022-24684, was fixed in Nomad 1.0.18, 1.1.12, and 1.2.6. | {'CVE-2022-24684'} | 2022-04-04T20:33:50Z | 2022-02-16T00:01:42Z | MODERATE | null | {'CWE-400'} | {'https://www.github.com/hashicorp/nomad', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24684', 'https://security.netapp.com/advisory/ntap-20220318-0008/', 'https://discuss.hashicorp.com/t/hcsec-2022-04-nomad-spread-job-stanza-may-trigger-panic-in-servers/35562'} | null |
Go | GHSA-6rrw-4fm9-rghv | Use of Hard-coded Cryptographic Key in Netmaker | Netmaker prior to versions 0.8.5, 0.9.4, 0.10.0, and 0.10.1 uses a hard-coded cryptographic key. | {'CVE-2022-0664'} | 2022-02-23T15:45:21Z | 2022-02-19T00:01:36Z | HIGH | null | {'CWE-321'} | {'https://github.com/gravitl/netmaker/commit/9bee12642986cb9534e268447b70e6f0f03c59cf', 'https://github.com/gravitl/netmaker', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0664', 'https://huntr.dev/bounties/29898a42-fd4f-4b5b-a8e3-ab573cb87eac'} | null |
Go | GHSA-rrp4-2xx3-mv29 | Command injection in gh-ost | Gh-ost version <= 1.1.2 allows users to inject DSN strings via the `-database` parameter.
This is a low severity vulnerability as the attacker must have access to the target host or trick an administrator into executing a malicious `gh-ost` command on a host running `gh-ost`, plus network access from host running `gh-ost` to the attack's malicious MySQL server.
### Impact
This issue may lead to arbitrary local file read.
### Patches
Fixed in 1.1.3+.
### Workarounds
None
### References
- https://advisory.dw1.io/51
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [github/gh-ost](http://github.com/github/gh-ost) | {'CVE-2022-21687'} | 2022-02-07T21:07:25Z | 2022-02-01T00:47:33Z | MODERATE | null | {'CWE-20', 'CWE-74'} | {'https://github.com/github/gh-ost', 'https://github.com/github/gh-ost/security/advisories/GHSA-rrp4-2xx3-mv29', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21687', 'https://github.com/github/gh-ost/commit/a91ab042de013cfd8fbb633763438932d9080d8f'} | null |
Go | GHSA-5wmg-j84w-4jj4 | Arbitrary File Write via Archive Extraction in mholt/archiver | mholt/archiver golang package before e4ef56d48eb029648b0e895bb0b6a393ef0829c3 is vulnerable to directory traversal, allowing attackers to write to arbitrary files via a ../ (dot dot slash) in an archive entry that is mishandled during extraction. This vulnerability is also known as 'Zip-Slip'. | {'CVE-2018-1002207'} | 2021-05-20T16:56:29Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-1002207', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMMHOLTARCHIVERCMDARCHIVER-50071', 'https://snyk.io/research/zip-slip-vulnerability', 'https://github.com/mholt/archiver/pull/65', 'https://github.com/mholt/archiver/commit/e4ef56d48eb029648b0e895bb0b6a393ef0829c3', 'https://github.com/snyk/zip-slip-vulnerability'} | null |
Go | GHSA-j756-f273-xhp4 | Import token permissions checking not enforced | (This advisory is canonically <https://advisories.nats.io/CVE/CVE-2021-3127.txt>)
## Problem Description
The NATS server provides for Subjects which are namespaced by Account; all Subjects are supposed to be private to an account, with an Export/Import system used to grant cross-account access to some Subjects. Some Exports are public, such that anyone can import the
relevant subjects, and some Exports are private, such that the Import requires a token JWT to prove permission.
The JWT library's validation of the bindings in the Import Token incorrectly warned on mismatches, instead of outright rejecting the token.
As a result, any account can take an Import token used by any other account and re-use it for themselves because the binding to the
importing account is not rejected, and use it to import *any* Subject from the Exporting account, not just the Subject referenced in the Import Token.
The NATS account-server system treats account JWTs as semi-public information, such that an attacker can easily enumerate all account JWTs and retrieve all Import Tokens from those account JWTs.
The CVE identifier should cover the JWT library repair and the nats-server containing the fixed JWT library, and any other application depending upon the fixed JWT library.
## Affected versions
#### JWT library
* all versions prior to 2.0.1
* fixed after nats-io/jwt#149 landed (2021-03-14)
#### NATS Server
* Version 2 prior to 2.2.0
+ 2.0.0 through and including 2.1.9 are vulnerable
* fixed with nats-io/nats-server@423b79440c (2021-03-14)
## Impact
In deployments with untrusted accounts able to update the Account Server with imports, a malicious account can access any Subject from an account which provides Exported Subjects.
Abuse of this facility requires the malicious actor to upload their tampered Account JWT to the Account Server, providing the service operator with a data-store which can be scanned for signs of abuse.
## Workaround
Deny access to clients to update their account JWT in the account server.
## Solution
Upgrade the JWT dependency in any application using it.
Upgrade the NATS server if using NATS Accounts (with private Exports; Account owners can create those at any time though).
Audit all accounts JWTs to scan for exploit attempts; a Python script to audit the accounts can be found at <https://gist.github.com/philpennock/09d49524ad98043ff11d8a40c2bb0d5a>. | null | 2021-05-20T21:01:49Z | 2021-05-21T16:22:20Z | CRITICAL | null | {'CWE-863'} | {'https://github.com/nats-io/nats-server/security/advisories/GHSA-j756-f273-xhp4'} | null |
Go | GHSA-579h-mv94-g4gp | Privilege Escalation in Kubernetes | In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection. | {'CVE-2018-1002105'} | 2021-05-20T20:40:04Z | 2022-02-15T01:57:18Z | CRITICAL | null | {'CWE-269'} | {'https://access.redhat.com/errata/RHSA-2018:3551', 'https://access.redhat.com/errata/RHSA-2018:3624', 'https://www.securityfocus.com/bid/106068', 'https://www.exploit-db.com/exploits/46053', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1002105', 'https://access.redhat.com/errata/RHSA-2018:3742', 'https://groups.google.com/forum/#!topic/kubernetes-announce/GVllWCg6L88', 'https://www.openwall.com/lists/oss-security/2019/06/28/2', 'https://lists.opensuse.org/opensuse-security-announce/2020-04/msg00041.html', 'https://github.com/kubernetes/kubernetes/issues/71411', 'https://www.exploit-db.com/exploits/46052/', 'https://github.com/kubernetes/kubernetes/commit/2257c1ecbe3c0cf71dd50b82752ae189c94ec905', 'https://www.exploit-db.com/exploits/46053/', 'https://www.openwall.com/lists/oss-security/2019/07/06/3', 'https://www.coalfire.com/The-Coalfire-Blog/December-2018/Kubernetes-Vulnerability-What-You-Can-Should-Do', 'https://access.redhat.com/errata/RHSA-2018:3754', 'https://access.redhat.com/errata/RHSA-2018:3752', 'https://access.redhat.com/errata/RHSA-2018:3537', 'https://access.redhat.com/errata/RHSA-2018:3598', 'https://access.redhat.com/errata/RHSA-2018:3549', 'https://github.com/evict/poc_CVE-2018-1002105', 'https://www.openwall.com/lists/oss-security/2019/07/06/4', 'https://security.netapp.com/advisory/ntap-20190416-0001/'} | null |
Go | GO-2020-0032 | null | Due to improper santization of user input, Controller.FileHandler allows
for directory traversal, allowing an attacker to read files outside of
the target directory that the server has permission to read.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/goadesign/goa/commit/70b5a199d0f813d74423993832c424e1fc73fb39', 'https://github.com/goadesign/goa/pull/2388'} | null |
Go | GO-2021-0096 | null | Due to improper setting of finalizers, memory passed to C may be freed before it is used,
leading to crashes due to memory corruption or possible code execution.
| {'CVE-2020-8945'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/proglottis/gpgme/pull/23', 'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733'} | null |
Go | GHSA-vc3x-gx6c-g99f | Denial of Service in Bytom | In the client in Bytom before 1.0.6, checkTopicRegister in p2p/discover/net.go does not prevent negative idx values, leading to a crash. | {'CVE-2018-18206'} | 2021-05-20T18:55:02Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-190'} | {'https://github.com/Bytom/bytom/commit/1ac3c8ac4f2b1e1df9675228290bda6b9586ba42', 'https://github.com/Bytom/bytom/pull/1307', 'https://nvd.nist.gov/vuln/detail/CVE-2018-18206'} | null |
Go | GO-2021-0079 | null | A malformed query can cause an out-of-bounds panic due to improper
validation of arguments. If processing queries from untrusted
parties, this may be used as a vector for denial of service
attacks.
| {'CVE-2018-18206'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/Bytom/bytom/commit/1ac3c8ac4f2b1e1df9675228290bda6b9586ba42', 'https://github.com/Bytom/bytom/pull/1307'} | null |
Go | GHSA-qj26-7grj-whg3 | Privilege Escalation in fscrypt | The pam_fscrypt module in fscrypt before 0.2.4 may incorrectly restore primary and supplementary group IDs to the values associated with the root user, which allows attackers to gain privileges via a successful login through certain applications that use Linux-PAM (aka pam). | {'CVE-2018-6558'} | 2021-05-20T21:04:58Z | 2021-06-23T17:18:49Z | MODERATE | null | null | {'https://nvd.nist.gov/vuln/detail/CVE-2018-6558', 'https://github.com/google/fscrypt/commit/3022c1603d968c22f147b4a2c49c4637dd1be91b', 'https://github.com/google/fscrypt/issues/77', 'https://github.com/google/fscrypt/commit/315f9b042237200174a1fb99427f74027e191d66', 'https://launchpad.net/bugs/1787548'} | null |
Go | GHSA-3pqh-p72c-fj85 | Improper Preservation of Permissions in github.com/cloudflare/cfrpki/cmd/octorpki | ### Impact
When copying files with rsync, octorpki uses the "-a" flag 0, which forces rsync to copy binaries with the suid bit set as root. Since the provided service definition defaults to root (https://github.com/cloudflare/cfrpki/blob/master/package/octorpki.service) this could allow for a vector, when combined with another vulnerability that causes octorpki to process a malicious TAL file, for a local privilege escalation.
## For more information
If you have any questions or comments about this advisory email us at security@cloudflare.com | {'CVE-2021-3978'} | 2021-11-19T13:10:27Z | 2021-11-19T19:34:26Z | MODERATE | null | {'CWE-281'} | {'https://github.com/cloudflare/cfrpki/security/advisories/GHSA-3pqh-p72c-fj85', 'https://github.com/cloudflare/cfrpki'} | null |
Go | GO-2020-0049 | null | Due to improper validation of caller input, validation is silently disabled
if the provided expected token is malformed, causing any user supplied token
to be considered valid.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/justinas/nosurf/pull/60', 'https://github.com/justinas/nosurf/commit/4d86df7a4affa1fa50ab39fb09aac56c3ce9c314'} | null |
Go | GHSA-599h-8wpj-75xj | Authentication Bypass in tyk-identity-broker | The package github.com/tyktechnologies/tyk-identity-broker before 1.1.1 are vulnerable to Authentication Bypass via the Go XML parser which can cause SAML authentication bypass. This is because the XML parser doesn’t guarantee integrity in the XML round-trip (encoding/decoding XML data). | {'CVE-2021-23365'} | 2021-05-20T21:24:49Z | 2021-06-23T17:23:30Z | CRITICAL | null | {'CWE-287'} | {'https://github.com/TykTechnologies/tyk-identity-broker/commit/46f70420e0911e4e8b638575e29d394c227c75d0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23365', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMTYKTECHNOLOGIESTYKIDENTITYBROKER-1089720', 'https://github.com/TykTechnologies/tyk-identity-broker/releases/tag/v1.1.1', 'https://github.com/TykTechnologies/tyk-identity-broker/commit/243092965b0f93a95a14cb882b5b9a3df61dd5c0', 'https://github.com/TykTechnologies/tyk-identity-broker/pull/147'} | null |
Go | GHSA-8vwm-8vj8-rqjf | User login denial of service in github.com/google/fscrypt | The PAM module for fscrypt doesn't adequately validate fscrypt metadata files, allowing users to create malicious metadata files that prevent other users from logging in. A local user can cause a denial of service by creating a fscrypt metadata file that prevents other users from logging into the system. We recommend upgrading to version 0.3.3 or above | {'CVE-2022-25327'} | 2022-03-01T19:27:43Z | 2022-02-26T00:00:44Z | MODERATE | null | {'CWE-276'} | {'https://github.com/google/fscrypt', 'https://nvd.nist.gov/vuln/detail/CVE-2022-25327', 'https://github.com/google/fscrypt/pull/346'} | null |
Go | GHSA-33p6-fx42-7rf5 | Harbor is vulnerable to a limited Server-Side Request Forgery (SSRF) (CVE-2020-13788) | # Impact
Matt Hamilton from Soluble has discovered a limited Server-Side Request Forgery (SSRF) that allowed Harbor project owners to scan the TCP ports of hosts on the Harbor server's internal network.
The vulnerability was immediately fixed by the Harbor team.
# Issue
The “Test Endpoint” API, part of the functionality for ensuring a project Webhook is accessible and functional, is vulnerable to a limited SSRF attack. A malicious user that is also a project administrator can use this API for internal port scanning.
# Known Attack Vectors
Successful exploitation of this issue will lead to bad actors identifying open TCP ports on any network that is accessible by the Harbor core services
# Patches
If your product uses the affected releases of Harbor, update to version 2.0.1 to patch this issue immediately.
https://github.com/goharbor/harbor/releases/tag/v2.0.1
# Workarounds
Since only project administrators (the user that created the project) are allowed to test the webhook endpoints configured in Harbor, a Harbor system administrator can control who is a project admin. In addition, Harbor system administrators can enforce a setting where only an administrator is allowed to create new projects instead of the default Everyone. This further restricts who can be a project administrator in Harbor.
# For more information
If you have any questions or comments about this advisory, contact cncf-harbor-security@lists.cncf.io
View our security policy at https://github.com/goharbor/harbor/security/policy
https://nvd.nist.gov/vuln/detail/CVE-2020-13788
https://www.soluble.ai/blog/harbor-ssrf-cve-2020-13788 | {'CVE-2020-13788'} | 2021-05-24T19:08:11Z | 2022-02-11T23:17:02Z | LOW | null | {'CWE-918'} | {'https://github.com/goharbor/harbor/security/advisories/GHSA-33p6-fx42-7rf5', 'https://www.youtube.com/watch?v=v8Isqy4yR3Q', 'https://www.soluble.ai/blog/harbor-ssrf-cve-2020-13788', 'https://github.com/goharbor/harbor/releases', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13788'} | null |
Go | GHSA-vj54-cjrx-x696 | Observable Discrepancy in Argo | Fixed in v1.5.1, Argo version v1.5.0 was vulnerable to a user-enumeration vulnerability which allowed attackers to determine the usernames of valid (non-SSO) accounts within Argo. | {'CVE-2020-11576'} | 2021-07-29T16:07:15Z | 2021-12-09T19:59:24Z | MODERATE | null | {'CWE-203'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-11576', 'https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1', 'https://www.soluble.ai/blog/argo-cves-2020', 'https://github.com/argoproj/argo-cd/pull/3215'} | null |
Go | GO-2021-0110 | null | Uniqueness of JWT IDs (jti) are not checked, allowing the JWT to be
replayed.
| {'CVE-2020-15222'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9', 'https://github.com/ory/fosite/security/advisories/GHSA-v3q9-2p3m-7g43'} | null |
Go | GHSA-h43v-26r7-7j4c | Allocation of Resources Without Limits or Throttling in HashiCorp Nomad | HashiCorp Nomad and Nomad Enterprise before 0.10.3 allow unbounded resource usage. | {'CVE-2020-7218'} | 2022-02-24T12:07:02Z | 2021-05-18T18:20:19Z | HIGH | null | {'CWE-400', 'CWE-770'} | {'https://github.com/hashicorp/nomad', 'https://www.hashicorp.com/blog/category/nomad/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7218', 'https://github.com/hashicorp/nomad/pull/7022', 'https://github.com/hashicorp/nomad/issues/7002'} | null |
Go | GHSA-25gf-8qrr-g78r | Missing SSL Certificate Validation in Hashicorp Consul | HashiCorp Consul before 1.10.1 (and Consul Enterprise) has Missing SSL Certificate Validation. xds does not ensure that the Subject Alternative Name of an upstream is validated. | {'CVE-2021-32574'} | 2021-07-29T14:53:57Z | 2021-07-19T21:21:03Z | HIGH | null | {'CWE-295'} | {'https://github.com/hashicorp/consul/releases/tag/v1.10.1', 'https://www.hashicorp.com/blog/category/consul', 'https://discuss.hashicorp.com/t/hcsec-2021-17-consul-s-envoy-tls-configuration-did-not-validate-destination-service-subject-alternative-names/26856', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32574'} | null |
Go | GHSA-q3j5-32m5-58c2 | Privilege Elevation in runc | libcontainer/user/user.go in runC before 0.1.0, as used in Docker before 1.11.2, improperly treats a numeric UID as a potential username, which allows local users to gain privileges via a numeric username in the password file in a container. | {'CVE-2016-3697'} | 2021-10-05T16:34:17Z | 2021-12-20T18:21:34Z | HIGH | null | null | {'https://rhn.redhat.com/errata/RHSA-2016-1034.html', 'https://security.gentoo.org/glsa/201612-28', 'https://rhn.redhat.com/errata/RHSA-2016-2634.html', 'https://github.com/docker/docker/issues/21436', 'https://lists.opensuse.org/opensuse-updates/2016-05/msg00111.html', 'https://github.com/opencontainers/runc/pull/708', 'https://github.com/opencontainers/runc', 'https://github.com/opencontainers/runc/commit/69af385de62ea68e2e608335cffbb0f4aa3db091', 'https://nvd.nist.gov/vuln/detail/CVE-2016-3697', 'https://github.com/opencontainers/runc/releases/tag/v0.1.0'} | null |
Go | GHSA-h3p9-wrgx-82cm | Use of a Broken or Risky Cryptographic Algorithm in Terraform | When using the Azure backend with a shared access signature (SAS), Terraform versions prior to 0.12.17 may transmit the token and state snapshot using cleartext HTTP. | {'CVE-2019-19316'} | 2021-05-13T15:15:38Z | 2021-05-18T18:18:50Z | HIGH | null | {'CWE-327', 'CWE-20'} | {'https://github.com/hashicorp/terraform/security/advisories/GHSA-4rvg-555h-r626', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19316', 'https://github.com/hashicorp/terraform/commit/6db3cf8e5b4cfb2a3cd1d99a813b50b2d5d363bb', 'https://github.com/hashicorp/terraform/issues/23493'} | null |
Go | GO-2020-0008 | null | DNS message transaction IDs are generated using [`math/rand`] which
makes them relatively predictable. This reduces the complexity
of response spoofing attacks against DNS clients.
| {'CVE-2019-19794'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/miekg/dns/issues/1043', 'https://github.com/miekg/dns/issues/1037', 'https://github.com/miekg/dns/pull/1044', 'https://github.com/miekg/dns/commit/8ebf2e419df7857ac8919baa05248789a8ffbf33'} | null |
Go | GHSA-5jgq-x857-p8xw | Account compromise in Evmos | ## Impact
_What kind of vulnerability is it? Who is impacted?_
### Classification
The vulnerability has been classified as `critical` with a score of `9.0` (highest). It has the potential to affect and drain unclaimed airdrop funds from Cosmos and Osmosis eligible user addresses.
### Disclosure
The attack requires advanced knowledge of the internals of the core and application packages of IBC, IBC relayers, the Cosmos SDK `AnteHandler`, and the Evmos `x/claims` module. The step-by-step attack is described below:
1. An actor creates a malicious chain with a custom `AnteHandler` that skips signature verification for transactions, specifically IBC `MsgTransfer`. This allows the attacker to impersonate any account by setting a custom `sender` address field of the IBC transfer message.
2. The malicious actor then connects this newly created chain via IBC to Evmos and fills the `recipient` address from the transfer message with an address they control.
3. Once the IBC packet containing the Transfer data is relayed to Evmos, it is processed by the claims module IBC middleware. Which migrates the claim records to the recipient address, which is owned by the attacker.
4. The attacker then performs two airdrop Actions, claiming up to 75% of the total initial claimable amount.
5. The Actor repeats steps 1., 2., and 3. for every address that has unclaimed funds from the airdrop. This automatically claims 75% of the unclaimable amount.
6. The malicious actor performs the final Action, claiming 100% of all the user funds.
7. Then, the attacker transfers the funds to another chain with a DEX (Osmosis, Cosmos Hub) via IBC.
8. Finally, the attacker withdraws the total amount in fiat through a centralized exchange.
### Users impacted
No users have suffered the loss of funds as no malicious chains have been connected to Evmos.
## Patches
_Has the problem been patched? What versions should users upgrade to?_
The patch involves defining a list of authorized channels for chains that are connected to Evmos via IBC. This restricts the chains that have the capability of migrating users' claims records as per the specification. By default, the authorized destination channels are `"channel-0"` (Osmosis) and `"channel-3"` (Cosmos Hub).
Please upgrade your mainnet node and validator to [`v2.0.1`](https://github.com/tharsis/evmos/releases/tag/v2.0.1) **ASAP**.
## Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
No, the fix for the critical vulnerability is state machine breaking. An upgrade procedure must be coordinated with the nodes running the network.
## References
_Are there any links users can visit to find out more?_
* Claims module spec: [evmos.dev/modules/claims](https://evmos.dev/modules/claims)
* Cosmos SDK documentation: [docs.cosmos.network](https://docs.cosmos.network/)
* IBC documentation: [ibc.cosmos.network](https://ibc.cosmos.network/)
## For more information
If you have any questions or comments about this advisory:
* Reach out to the Core Team in [Discord](https://discord.gg/evmos)
* Open an issue in [tharsis/evmos](http://github.com/tharsis/evmos/issues)
* Email us at [security@thars.is](security@thars.is)
Thanks to the Core IBC team at Interchain GmbH for the secure disclosure of this vulnerability | {'CVE-2022-24738'} | 2022-03-18T20:07:34Z | 2022-03-07T21:45:59Z | HIGH | null | {'CWE-287'} | {'https://github.com/tharsis/evmos/releases/tag/v2.0.1', 'https://github.com/tharsis/evmos/security/advisories/GHSA-5jgq-x857-p8xw', 'https://github.com/tharsis/evmos', 'https://github.com/tharsis/evmos/commit/28870258d4ee9f1b8aeef5eba891681f89348f71', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24738'} | null |
Go | GHSA-6qfg-8799-r575 | Symlink Attack | The Kubernetes kubectl cp command in versions 1.1-1.12, and versions prior to 1.13.11, 1.14.7, and 1.15.4 allows a combination of two symlinks provided by tar output of a malicious container to place a file outside of the destination directory specified in the kubectl cp invocation. This could be used to allow an attacker to place a nefarious file using a symlink, outside of the destination tree. | {'CVE-2019-11251'} | 2021-05-17T21:58:06Z | 2021-05-18T15:30:07Z | MODERATE | null | {'CWE-59', 'CWE-61'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-11251', 'https://groups.google.com/d/msg/kubernetes-announce/YYtEFdFimZ4/nZnOezZuBgAJ', 'https://github.com/kubernetes/kubernetes/pull/82143', 'https://github.com/kubernetes/kubernetes/issues/87773'} | null |
Go | GHSA-69j6-29vr-p3j9 | Authentication bypass for viewing and deletions of snapshots | Today we are releasing Grafana 7.5.11, and 8.1.6. These patch releases include an important security fix for an issue that affects all Grafana versions from 2.0.1.
[Grafana Cloud](https://grafana.com/cloud) instances have already been patched and an audit did not find any usage of this attack vector. [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.
8.1.5 contained a single fix for bar chart panels. We believe that users can expedite deployment by moving from 8.1.4 to 8.1.6 directly.
## CVE-2021-39226 Snapshot authentication bypass
### Summary
CVSS Score: 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
We received a security report to [security@grafana.com](mailto:security@grafana.com) on 2021-09-15 about a vulnerability in Grafana regarding the snapshot feature. It was later identified as affecting Grafana versions from 2.0.1 to 8.1.6. [CVE-2021-39226](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39226) has been assigned to this vulnerability.
### Impact
Unauthenticated and authenticated users are able to view the snapshot with the lowest database key by accessing the literal paths:
* `/dashboard/snapshot/:key`, or
* `/api/snapshots/:key`
If the snapshot "public_mode" configuration setting is set to true (vs default of false), unauthenticated users are able to delete the snapshot with the lowest database key by accessing the literal path:
* `/api/snapshots-delete/:deleteKey`
Regardless of the snapshot "public_mode" setting, authenticated users are able to delete the snapshot with the lowest database key by accessing the literal paths:
* `/api/snapshots/:key`, or
* `/api/snapshots-delete/:deleteKey`
The combination of deletion and viewing enables a complete walk through all snapshot data while resulting in complete snapshot data loss.
### Attack audit
While we can not guarantee that the below will identify all attacks, if you do find something with the below, you should consider doing a full assessment.
#### Through reverse proxy/load balancer logs
To determine if your Grafana installation has been exploited for this vulnerability, search through your reverse proxy/load balancer access logs for instances where the path is `/dashboard/snapshot/:key`, `/api/snapshots/:key` or `/api/snapshots-delete/:deleteKey`, and the response status code was 200 (OK).
For example, if you’re using the Kubernetes ingress-nginx controller and sending logs to Loki, use a LogQL query like `{job="nginx-ingress-controller"} |= "\"status\": 200" |= "\"uri\": \"/api/snapshots/:key\""`.
#### Through the Grafana Enterprise audit feature
If you enabled “Log web requests” in your configuration with `router_logging = true`, look for
`"requestUri":"/api/snapshots-delete/”`,`“requestUri":"/api/snapshots/:key"`, or `"type":"snapshot"` in combination with `"action":"delete"`.
### Patched versions
Release 8.1.6:
- [Download Grafana 8.1.6](https://grafana.com/grafana/download/8.1.6)
- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-1-6/)
Release 7.5.11:
- [Download Grafana 7.5.11](https://grafana.com/grafana/download/7.5.11)
- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-7-5-11/)
### Solutions and mitigations
Download and install the appropriate patch for your version of Grafana.
[Grafana Cloud](https://grafana.com/cloud) instances have already been patched, and [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.
### Workaround
If for some reason you cannot upgrade:
You can use a reverse proxy or similar to block access to the literal paths
* `/api/snapshots/:key`
* `/api/snapshots-delete/:deleteKey`
* `/dashboard/snapshot/:key`
* `/api/snapshots/:key`
They have no normal function and can be disabled without side effects.
### Timeline and postmortem
Here is a detailed timeline starting from when we originally learned of the issue. All times in UTC.
* 2021-09-15 14:49: Tuan Tran theblackturtle0901@gmail.com sends initial report about viewing snapshots without authentication
* 2021-09-15 15:56: Initial reproduction
* 2021-09-15 17:10: MEDIUM severity declared
* 2021-09-15 18:58: Workaround deployed on Grafana Cloud
* 2021-09-15 19:15: `/api/snapshots/:key` found to be vulnerable as well
* 2021-09-15 19:30: `/api/snapshots/:key` blocked on Grafana Cloud
* 2021-09-16 09:31: `/api/snapshots-delete/:deleteKey` found to be vulnerable as well, blocked on Grafana Cloud. From this point forward, Cloud is not affected any more.
* 2021-09-16 09:35: HIGH severity declared
* 2021-09-16 11:19: Realization that combination of deletion and viewing allows enumeration and permanent DoS
* 2021-09-16 11:19: CRITICAL declared
* 2021-09-17 10:53: Determination that no weekend work is needed. While issue is CRITICAL, scope is very limited
* 2021-09-17 14:26: Audit of Grafana Cloud concluded, no evidence of exploitation
* 2021-09-23: Grafana Cloud instances updated
* 2021-09-28 12:00: Grafana Enterprise images released to customers under embargo
* 2021-10-05 17:00: Public release
## Reporting security issues
If you think you have found a security vulnerability, please send a report to [security@grafana.com](mailto:security@grafana.com). This address can be used for all of
Grafana Labs's open source and commercial products (including but not limited to Grafana, Tempo, Loki, Amixr, k6, Tanka, and Grafana Cloud, Grafana Enterprise, and grafana.com). We only accept vulnerability reports at this address. We would prefer that you encrypt your message to us using our PGP key. The key fingerprint is:
F988 7BEA 027A 049F AE8E 5CAA D125 8932 BE24 C5CA
The key is available from [keys.gnupg.net](http://keys.gnupg.net/pks/lookup?op=get&fingerprint=on&search=0xD1258932BE24C5CA) by searching for [security@grafana](http://keys.gnupg.net/pks/lookup?search=security@grafana&fingerprint=on&op=index.
## Security announcements
We maintain a category on the community site named [Security Announcements](https://community.grafana.com/c/security-announcements),
where we will post a summary, remediation, and mitigation details for any patch containing security fixes. You can also subscribe to email updates to this category if you have a grafana.com account and sign in to the community site, or via updates from our [Security Announcements RSS feed](https://community.grafana.com/c/security-announcements.rss).
## Acknowledgement
We would like to thank [Tran Viet Tuan](https://github.com/theblackturtle) for responsibly disclosing the initially discovered vulnerability to us. | {'CVE-2021-39226'} | 2021-11-18T15:13:27Z | 2021-10-05T20:24:02Z | HIGH | null | {'CWE-287'} | {'https://grafana.com/docs/grafana/latest/release-notes/release-notes-7-5-11/', 'https://github.com/grafana/grafana', 'https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-1-6/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/E6ANHRDBXQT6TURLP2THM26ZPDINFBEG/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39226', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DCKBFUSY6V4VU5AQUYWKISREZX5NLQJT/', 'http://www.openwall.com/lists/oss-security/2021/10/05/4', 'https://github.com/grafana/grafana/security/advisories/GHSA-69j6-29vr-p3j9', 'https://github.com/grafana/grafana/commit/2d456a6375855364d098ede379438bf7f0667269', 'https://security.netapp.com/advisory/ntap-20211029-0008/'} | null |
Go | GO-2021-0106 | null | Due to improper path santization, archives containing relative file
paths can cause files to be written (or overwritten) outside of the
target directory.
| null | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/whyrusleeping/tar-utils/commit/20a61371de5b51380bbdb0c7935b30b0625ac227', 'https://snyk.io/research/zip-slip-vulnerability'} | null |
Go | GHSA-rrfw-hg9m-j47h | Signature Validation Bypass | ### Impact
An authentication bypass exists in the [goxmldsig](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7) this library uses to determine if SAML assertions are genuine. An attacker could craft a SAML response that would appear to be valid but would not have been genuinely issued by the IDP.
### Patches
Version 0.4.2 bumps the dependency which should fix the issue.
### For more information
Please see [the advisory in goxmldsig](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7)
## Credits
The original vulnerability was discovered by @jupenur. Thanks to @russellhaering for the heads up. | null | 2021-10-08T21:25:26Z | 2021-05-24T16:59:42Z | CRITICAL | null | {'CWE-347'} | {'https://github.com/russellhaering/goxmldsig', 'https://github.com/crewjam/saml/security/advisories/GHSA-rrfw-hg9m-j47h'} | null |
Linux | GSD-2022-1000127 | net: fix information leakage in /proc/net/ptype | net: fix information leakage in /proc/net/ptype
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v4.19.228 by commit b67ad6170c0ea87391bb253f35d1f78857736e54, it was introduced in version v2.6.26 by commit 2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50. For more details please see the references link. | null | 2022-02-19T12:51:54.113867Z | 2022-02-18T21:44:08.303868Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50'} |
Linux | GSD-2022-1000577 | mm/kmemleak: avoid scanning potential huge holes | mm/kmemleak: avoid scanning potential huge holes
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.15.22 by commit a5389c80992f0001ee505838fe6a8b20897ce96e. For more details please see the references link. | null | 2022-03-07T01:52:49.916468Z | 2022-02-27T03:25:56.627026Z | null | null | null | null | null |
Linux | GSD-2022-1001736 | ath11k: fix kernel panic during unload/load ath11k modules | ath11k: fix kernel panic during unload/load ath11k modules
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.15.34 by commit c4b7653af62a9a5efe2856183d1f987c5429758b. For more details please see the references link. | null | 2022-04-25T06:55:36.049642Z | 2022-04-24T21:38:22.995962Z | null | null | null | null | null |
Linux | GSD-2022-1000824 | xen/xenbus: don't let xenbus_grant_ring() remove grants in error case | xen/xenbus: don't let xenbus_grant_ring() remove grants in error case
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.10.105 by commit 5c600371b8fd02cbbb0eb83a9f664e3f0b75c28e. For more details please see the references link. | null | 2022-03-18T02:55:46.065465Z | 2022-03-18T00:21:34.736307Z | null | null | null | null | null |
Linux | GSD-2021-1002266 | ALSA: gus: fix null pointer dereference on pointer block | ALSA: gus: fix null pointer dereference on pointer block
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.4.162 by commit c6d2cefdd05c4810c416fb8d384b5c377bd977bc. For more details please see the references link. | null | 2021-12-19T22:11:21.758827Z | 2021-11-29T02:36:06.886894Z | null | null | null | null | null |
Linux | GSD-2022-1001366 | net: sfc: add missing xdp queue reinitialization | net: sfc: add missing xdp queue reinitialization
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.16.20 by commit b8c46bc358d84701e7f7ffa054037db25f25da0e, it was introduced in version v5.5 by commit 3990a8fffbdad5765f47ea593f9de66c91762059. For more details please see the references link. | null | 2022-04-25T05:34:57.121574Z | 2022-04-24T21:08:21.160842Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/3990a8fffbdad5765f47ea593f9de66c91762059'} |
Linux | GSD-2021-1002636 | net/packet: rx_owner_map depends on pg_vec | net/packet: rx_owner_map depends on pg_vec
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v4.14.259 by commit a829ff7c8ec494eca028824628a964cde543dc76, it was introduced in version v4.14.175 by commit 2975472e042e0bbfeeabddc5023cb8c011ec5a07. For more details please see the references link. | null | 2022-01-11T05:58:22.905108Z | 2021-12-27T05:28:20.479872Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/2975472e042e0bbfeeabddc5023cb8c011ec5a07'} |
Linux | GSD-2021-1001919 | ocfs2: mount fails with buffer overflow in strlen | ocfs2: mount fails with buffer overflow in strlen
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v4.4.290 by commit ac011cb3ff7a76b3e0e6e77158ee4ba2f929e1fb. For more details please see the references link. | null | 2021-12-20T01:29:47.500516Z | 2021-11-14T15:11:43.526270Z | null | null | null | null | null |
Linux | GSD-2021-1002323 | iavf: don't clear a lock we don't hold | iavf: don't clear a lock we don't hold
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.15.5 by commit c3db4fffb364ac7bf602de115afe69c32a46383c, it was introduced in version v4.17 by commit 640a8af5841fd66a26e26f5b9fb5476a3755852a. For more details please see the references link. | null | 2021-12-19T23:06:44.006988Z | 2021-11-29T02:38:44.091848Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/640a8af5841fd66a26e26f5b9fb5476a3755852a'} |
Linux | GSD-2022-1001389 | netlabel: fix out-of-bounds memory accesses | netlabel: fix out-of-bounds memory accesses
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.0 by commit 5578de4834fe0f2a34fedc7374be691443396d1f, it was introduced in version v2.6.19 by commit 446fda4f26822b2d42ab3396aafcedf38a9ff2b6. For more details please see the references link. | null | 2022-04-25T07:14:23.090107Z | 2022-04-24T21:09:57.160701Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/446fda4f26822b2d42ab3396aafcedf38a9ff2b6'} |
Linux | GSD-2022-1001673 | irqchip/gic-v3: Fix GICR_CTLR.RWP polling | irqchip/gic-v3: Fix GICR_CTLR.RWP polling
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.15.34 by commit 7218a789abb3e033f5f3a85636ca50d9ae7b0fc9, it was introduced in version v3.17 by commit 021f653791ad17e03f98aaa7fb933816ae16f161. For more details please see the references link. | null | 2022-04-25T05:35:18.617538Z | 2022-04-24T21:33:57.749127Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/021f653791ad17e03f98aaa7fb933816ae16f161'} |
Linux | GSD-2022-1000961 | ep93xx: clock: Fix UAF in ep93xx_clk_register_gate() | ep93xx: clock: Fix UAF in ep93xx_clk_register_gate()
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.17.4 by commit 0f12166872da46c6b57ba2f1314bbf310b3bf017, it was introduced in version v5.16 by commit 9645ccc7bd7a16cd73c3be9dee70cd702b03be37. For more details please see the references link. | null | 2022-04-25T04:45:19.917726Z | 2022-04-24T20:35:21.847038Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/9645ccc7bd7a16cd73c3be9dee70cd702b03be37'} |
Linux | GSD-2021-1002773 | hamradio: defer ax25 kfree after unregister_netdev | hamradio: defer ax25 kfree after unregister_netdev
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v4.4.297 by commit b5b193d0c67180fefdc664650138e3b7959df615. For more details please see the references link. | null | 2022-01-11T05:47:03.049600Z | 2021-12-30T02:42:51.027043Z | null | null | null | null | null |
Linux | GSD-2022-1001223 | vfio/pci: fix memory leak during D3hot to D0 transition | vfio/pci: fix memory leak during D3hot to D0 transition
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.17.2 by commit c8a1f8bd586ee31020614b8d48b702ece3e2ae44, it was introduced in version v5.1 by commit 51ef3a004b1eb6241e56b3aa8495769a092a4dc2. For more details please see the references link. | null | 2022-04-25T06:06:11.525862Z | 2022-04-24T20:55:32.545235Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/51ef3a004b1eb6241e56b3aa8495769a092a4dc2'} |
Linux | GSD-2021-1002289 | f2fs: fix incorrect return value in f2fs_sanity_check_ckpt() | f2fs: fix incorrect return value in f2fs_sanity_check_ckpt()
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.10.82 by commit 7a5439474e69ddfe2921338ee1036bb730a56f26, it was introduced in version v5.10.67 by commit 74d6dfcb0f9daa0fd32368147c34cff05026eb4a. For more details please see the references link. | null | 2021-12-20T01:15:39.069523Z | 2021-11-29T02:37:12.846035Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/74d6dfcb0f9daa0fd32368147c34cff05026eb4a'} |
Linux | GSD-2022-1000598 | select: Fix indefinitely sleeping task in poll_schedule_timeout() | select: Fix indefinitely sleeping task in poll_schedule_timeout()
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.16.4 by commit 0c919af28a1b3b94393bebd1750912c80e61148f. For more details please see the references link. | null | 2022-03-07T01:48:04.880707Z | 2022-02-27T03:29:01.194938Z | null | null | null | null | null |
Linux | GSD-2022-1000062 | parisc: Clear stale IIR value on instruction access rights trap | parisc: Clear stale IIR value on instruction access rights trap
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.15.13 by commit e96373f0a5f484bc1e193f9951dcb3adf24bf3f7. For more details please see the references link. | null | 2022-01-11T05:51:01.923438Z | 2022-01-10T19:52:26.203834Z | null | null | null | null | null |
Linux | GSD-2022-1000432 | ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path | ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.15.24 by commit 3cab045c99dbb9a94eb2d1d405f399916eec698a, it was introduced in version v4.0 by commit f243e5a7859a24d10975afb9a1708cac624ba6f1. For more details please see the references link. | null | 2022-03-07T01:45:26.008233Z | 2022-02-27T03:06:40.005191Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/f243e5a7859a24d10975afb9a1708cac624ba6f1'} |
Linux | GSD-2021-1000467 | netfilter: nftables: avoid overflows in nft_hash_buckets() | netfilter: nftables: avoid overflows in nft_hash_buckets()
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v4.14.233 by commit 2824cafc6a93792d9ad85939c499161214d84c4b, it was introduced in version v4.9 by commit 0ed6389c483dc77cdbdd48de0ca7ce41723dd667. For more details please see the references link. | null | 2021-12-19T23:02:32.905545Z | 2021-05-31T15:39:45.041586Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/0ed6389c483dc77cdbdd48de0ca7ce41723dd667'} |
Linux | GSD-2021-1000037 | ARM: footbridge: fix PCI interrupt mapping | ARM: footbridge: fix PCI interrupt mapping
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.10.32 by commit 1fc087fdb98d556b416c82ed6e3964a30885f47a, it was introduced in version v4.13 by commit 30fdfb929e82450bbf3d0e0aba56efbc29b52b52. For more details please see the references link. | null | 2021-12-20T00:22:51.195031Z | 2021-05-31T15:39:45.031586Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/30fdfb929e82450bbf3d0e0aba56efbc29b52b52'} |
Linux | GSD-2021-1001276 | scsi: iscsi: Fix conn use after free during resets | scsi: iscsi: Fix conn use after free during resets
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.10.52 by commit 89812e7957ab0746eab66ed6fc49d52bb4dca250. For more details please see the references link. | null | 2021-12-20T01:25:33.162298Z | 2021-08-03T01:55:30.324863Z | null | null | null | null | null |
Linux | GSD-2022-1001809 | virt: acrn: fix a memory leak in acrn_dev_ioctl() | virt: acrn: fix a memory leak in acrn_dev_ioctl()
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.15.33 by commit 1d5103d9bb7d42fc220afe9f01ec6b9fe0ea5773, it was introduced in version v5.12 by commit 9c5137aedd112f78a968bdd2325de2ea06df46c0. For more details please see the references link. | null | 2022-04-25T06:03:22.237971Z | 2022-04-24T21:43:45.525157Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/9c5137aedd112f78a968bdd2325de2ea06df46c0'} |
Linux | GSD-2021-1000934 | net: bridge: fix vlan tunnel dst null pointer dereference | net: bridge: fix vlan tunnel dst null pointer dereference
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.4.128 by commit a2241e62f6b4a774d8a92048fdf59c45f6c2fe5c, it was introduced in version v4.11 by commit 11538d039ac6efcf4f1a6c536e1b87cd3668a9fd. For more details please see the references link. | null | 2021-12-19T22:41:33.702067Z | 2021-06-30T00:25:28.857061Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/11538d039ac6efcf4f1a6c536e1b87cd3668a9fd'} |
Linux | GSD-2021-1001626 | drm/nouveau: avoid a use-after-free when BO init fails | drm/nouveau: avoid a use-after-free when BO init fails
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.10.73 by commit f86e19d918a85492ad1a01fcdc0ad5ecbdac6f96, it was introduced in version v5.4 by commit 019cbd4a4feb3aa3a917d78e7110e3011bbff6d5. For more details please see the references link. | null | 2021-12-19T23:38:20.844121Z | 2021-10-19T16:28:52.373603Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/019cbd4a4feb3aa3a917d78e7110e3011bbff6d5'} |
Linux | GSD-2022-1002376 | NFSD: prevent integer overflow on 32 bit systems | NFSD: prevent integer overflow on 32 bit systems
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v4.19.238 by commit 3a2789e8ccb4a3e2a631f6817a2d3bb98b8c4fd8. For more details please see the references link. | null | 2022-04-25T05:55:31.585216Z | 2022-04-24T22:40:39.560485Z | null | null | null | null | null |
Linux | GSD-2022-1002399 | jfs: prevent NULL deref in diFree | jfs: prevent NULL deref in diFree
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v4.14.276 by commit 33bd243566a9b1ca94261dcc2e16c7b9e3a71c15. For more details please see the references link. | null | 2022-04-25T05:32:37.736659Z | 2022-04-24T22:43:17.758616Z | null | null | null | null | null |
Linux | GSD-2021-1001333 | iommu/arm-smmu: Fix arm_smmu_device refcount leak when arm_smmu_rpm_get fails | iommu/arm-smmu: Fix arm_smmu_device refcount leak when arm_smmu_rpm_get fails
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.4.134 by commit 3761ae0d0e549f2acdaf11f49df4ed06d256b20f. For more details please see the references link. | null | 2021-12-19T23:49:23.459363Z | 2021-08-03T02:11:21.391461Z | null | null | null | null | null |
Linux | GSD-2021-1001299 | virtio-net: Add validation for used length | virtio-net: Add validation for used length
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.10.51 by commit c92298d228f61589dd21657af2bea95fc866b813. For more details please see the references link. | null | 2021-12-20T00:29:04.560764Z | 2021-08-03T02:01:11.969225Z | null | null | null | null | null |
Linux | GSD-2022-1002233 | mxser: fix xmit_buf leak in activate when LSR == 0xff | mxser: fix xmit_buf leak in activate when LSR == 0xff
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.4.189 by commit 996291d06851a26678a0fab488b6e1f0677c0576, it was introduced in version v2.6.33 by commit 6769140d304731f0a3b177470a2adb4bacd9036b. For more details please see the references link. | null | 2022-04-25T03:24:00.102407Z | 2022-04-24T22:24:11.817751Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/6769140d304731f0a3b177470a2adb4bacd9036b'} |
Linux | GSD-2021-1000871 | net/qla3xxx: fix schedule while atomic in ql_sem_spinlock | net/qla3xxx: fix schedule while atomic in ql_sem_spinlock
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v4.19.195 by commit 92473994deec84b46ba98700810f2a025a30a9e1. For more details please see the references link. | null | 2021-12-19T23:16:27.772574Z | 2021-06-30T00:02:42.481312Z | null | null | null | null | null |
Linux | GSD-2021-1001763 | drm/amd/pm: Update intermediate power state for SI | drm/amd/pm: Update intermediate power state for SI
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.14.9 by commit 06a18e64256f7aecb5a27df02faa3568fcd3c105. For more details please see the references link. | null | 2021-12-20T01:17:24.031243Z | 2021-10-19T16:35:33.763350Z | null | null | null | null | null |
Linux | GSD-2021-1000522 | Bluetooth: SMP: Fail if remote and local public keys are identical | Bluetooth: SMP: Fail if remote and local public keys are identical
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.10.40 by commit d8d261c7cfb3a5dd921b4aeeb944718afc3f3961, it was introduced in version v3.17 by commit bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9. For more details please see the references link. | null | 2021-12-19T23:32:57.044681Z | 2021-05-31T23:50:32.873245Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9'} |
Linux | GSD-2021-1000488 | mtd: require write permissions for locking and badblock ioctls | mtd: require write permissions for locking and badblock ioctls
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v4.4.269 by commit f4d28d8b9b0e7c4ae04214b8d7e0b0466ec6bcaf, it was introduced in version v4.4.233 by commit 1c9f9125892a43901438bf704ada6b7019e2a884. For more details please see the references link. | null | 2021-12-19T23:56:53.572567Z | 2021-05-31T15:39:45.041586Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/1c9f9125892a43901438bf704ada6b7019e2a884'} |
Linux | GSD-2021-1000172 | media: dvbdev: Fix memory leak in dvb_media_device_free() | media: dvbdev: Fix memory leak in dvb_media_device_free()
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.4.118 by commit 9185b3b1c143b8da409c19ac5a785aa18d67a81b, it was introduced in version v4.5 by commit 0230d60e4661d9ced6fb0b9a30f182ebdafbba7a. For more details please see the references link. | null | 2021-12-20T01:14:57.517914Z | 2021-05-31T15:39:45.031586Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/0230d60e4661d9ced6fb0b9a30f182ebdafbba7a'} |
Linux | GSD-2021-1002661 | scsi: scsi_debug: Sanity check block descriptor length in resp_mode_select() | scsi: scsi_debug: Sanity check block descriptor length in resp_mode_select()
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v4.19.222 by commit 04181973c38f3d6a353f9246dcf7fee08024fd9e. For more details please see the references link. | null | 2022-01-11T05:52:29.170431Z | 2021-12-27T05:34:46.679564Z | null | null | null | null | null |
Linux | GSD-2022-1001331 | ALSA: pcm: Fix races among concurrent hw_params and hw_free calls | ALSA: pcm: Fix races among concurrent hw_params and hw_free calls
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.17.1 by commit 1bbf82d9f961414d6c76a08f7f843ea068e0ab7b. For more details please see the references link. | null | 2022-04-25T04:22:49.824077Z | 2022-04-24T21:05:09.865064Z | null | null | null | null | null |
Linux | GSD-2021-1002231 | scsi: advansys: Fix kernel pointer leak | scsi: advansys: Fix kernel pointer leak
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v4.9.291 by commit ad19f7046c24f95c674fbea21870479b2b9f5bab. For more details please see the references link. | null | 2021-12-20T00:06:21.303185Z | 2021-11-29T02:34:27.378139Z | null | null | null | null | null |
Linux | GSD-2022-1001761 | ubifs: Fix read out-of-bounds in ubifs_wbuf_write_nolock() | ubifs: Fix read out-of-bounds in ubifs_wbuf_write_nolock()
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.15.33 by commit a7054aaf1909cf40489c0ec1b728fdcf79c751a6, it was introduced in version v2.6.27 by commit 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d. For more details please see the references link. | null | 2022-04-25T05:26:32.532508Z | 2022-04-24T21:40:41.967241Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d'} |
Linux | GSD-2022-1000873 | net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() | net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe()
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.4.183 by commit e50c589678e50f8d574612e473ca60ef45190896, it was introduced in version v3.18 by commit 8c14f9c70327a6fb75534c4c61d7ea9c82ccf78f. For more details please see the references link. | null | 2022-03-18T02:45:49.738634Z | 2022-03-18T00:26:31.836447Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/8c14f9c70327a6fb75534c4c61d7ea9c82ccf78f'} |
Linux | GSD-2022-1000520 | net: dsa: mv88e6xxx: fix use-after-free in mv88e6xxx_mdios_unregister | net: dsa: mv88e6xxx: fix use-after-free in mv88e6xxx_mdios_unregister
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.16.10 by commit 402888280890bceb19e96733dc44792ebfdcd62d, it was introduced in version v5.16.10 by commit 1b451c3994a2d322f8e55032c62c8b47b7d95900. For more details please see the references link. | null | 2022-02-27T03:18:48.091183Z | 2022-02-27T03:18:48.091183Z | null | null | null | null | {'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux//commit/1b451c3994a2d322f8e55032c62c8b47b7d95900'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.