ecosystem
stringclasses 11
values | vuln_id
stringlengths 10
19
| summary
stringlengths 4
220
⌀ | details
stringlengths 34
13.5k
| aliases
stringlengths 17
87
⌀ | modified_date
stringdate 2019-03-26 14:13:00
2022-05-10 08:46:52
| published_date
stringdate 2012-06-17 03:41:00
2022-05-10 08:46:50
| severity
stringclasses 5
values | score
float64 0
10
⌀ | cwe_id
stringclasses 581
values | refs
stringlengths 82
11.6k
| introduced
stringclasses 843
values | code_refs
stringlengths 46
940
| commits
stringlengths 46
940
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Go | GHSA-vpx7-vm66-qx8r | Path Traversal in github.com/unknwon/cae/zip | The ExtractTo function doesn't securely escape file paths in zip archives which include leading or non-leading "..". This allows an attacker to add or replace files system-wide. | {'CVE-2020-7664'} | 2022-01-04T19:33:01Z | 2021-05-18T20:31:06Z | HIGH | null | {'CWE-22'} | {'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMUNKNWONCAEZIP-570383', 'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11', 'https://github.com/unknwon/cae/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7664'} | null | {'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11'} | {'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11'} |
Go | GHSA-hcw3-j74m-qc58 | Incorrect Calculation in github.com/open-policy-agent/opa | ### Impact
Under certain conditions, pretty-printing an AST that contains synthetic nodes could change the logic of some statements by reordering array literals. Example of policies impacted are those that parse and compare web paths, see the example below.
**All of these** three conditions have to be met to create an adverse effect:
1. An AST of Rego had to be **created programmatically** such that it ends up containing terms without a location (such as wildcard variables).
2. The AST had to be **pretty-printed** using the `github.com/open-policy-agent/opa/format` package.
3. The result of the pretty-printing had to be **parsed and evaluated again** via an OPA instance using the bundles, or the Golang packages.
If any of these three conditions are not met, you are not affected.
Notably, all three would be true if using **optimized bundles**, i.e. bundles created with `opa build -O=1` or higher.
In that case, the optimizer would fulfil condition (1.), the result of that would be pretty-printed when writing the bundle to disk, fulfilling (2.). When the bundle was then used, we'd satisfy (3.).
#### Example
For example, the process outlined above could turn
this rule
```rego
hello {
["foo", _] = split(input.resource, "/")
}
```
into
```rego
hello {
[_, "foo"] = split(input.resource, "/")
}
```
with an input of
```rego
{
"resource": "foo/bar"
}
```
the result would change from
```rego
{
"hello": true
}
```
to (no default value of hello)
```rego
{}
```
The severity was determined to be *moderate* because the conditions are quite particular. Please note that its only the OPA bundle build process thats affected. An OPA sidecar of version 0.36.0 with an optimized bundle built by OPA 0.32.1 would not face this bug.
### Patches
Fixed in version 0.37.2.
### Workarounds
- Disabling optimization when creating bundles.
### References
- Introduced in https://github.com/open-policy-agent/opa/pull/3851
- Backported for the 0.33.1 patch release: https://github.com/open-policy-agent/opa/commit/bfd984ddf93ef2c4963a08d4fdadae0bcf1a3717
- Fixed by https://github.com/open-policy-agent/opa/commit/932e4ffc37a590ace79e9b75ca4340288c220239 and https://github.com/open-policy-agent/opa/commit/2bd8edab9e10e2dc9cf76ae8335ced0c224f3055
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Community Discussions](https://github.com/open-policy-agent/community/discussions/categories/opa-and-rego)
* Ask in Slack: https://slack.openpolicyagent.org/ | {'CVE-2022-23628'} | 2022-02-23T22:04:25Z | 2022-02-09T22:17:37Z | MODERATE | null | {'CWE-682'} | {'https://github.com/open-policy-agent/opa/commit/bfd984ddf93ef2c4963a08d4fdadae0bcf1a3717', 'https://github.com/open-policy-agent/opa/pull/3851', 'https://github.com/open-policy-agent/opa', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23628', 'https://github.com/open-policy-agent/opa/commit/932e4ffc37a590ace79e9b75ca4340288c220239', 'https://github.com/open-policy-agent/opa/security/advisories/GHSA-hcw3-j74m-qc58'} | null | {'https://github.com/open-policy-agent/opa/commit/bfd984ddf93ef2c4963a08d4fdadae0bcf1a3717', 'https://github.com/open-policy-agent/opa/commit/932e4ffc37a590ace79e9b75ca4340288c220239'} | {'https://github.com/open-policy-agent/opa/commit/bfd984ddf93ef2c4963a08d4fdadae0bcf1a3717', 'https://github.com/open-policy-agent/opa/commit/932e4ffc37a590ace79e9b75ca4340288c220239'} |
Go | GHSA-58v3-j75h-xr49 | Improper Input Validation in libseccomp-golang | libseccomp-golang 0.9.0 and earlier incorrectly generates BPFs that OR multiple arguments rather than ANDing them. A process running under a restrictive seccomp filter that specified multiple syscall arguments could bypass intended access restrictions by specifying a single matching argument. | {'CVE-2017-18367'} | 2021-05-17T15:26:35Z | 2021-05-18T15:44:30Z | HIGH | null | {'CWE-284'} | {'https://github.com/seccomp/libseccomp-golang/issues/22', 'https://lists.debian.org/debian-lts-announce/2020/08/msg00016.html', 'https://access.redhat.com/errata/RHSA-2019:4087', 'http://www.openwall.com/lists/oss-security/2019/04/25/6', 'https://access.redhat.com/errata/RHSA-2019:4090', 'https://usn.ubuntu.com/4574-1/', 'https://github.com/seccomp/libseccomp-golang/commit/06e7a29f36a34b8cf419aeb87b979ee508e58f9e', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18367'} | null | {'https://github.com/seccomp/libseccomp-golang/commit/06e7a29f36a34b8cf419aeb87b979ee508e58f9e'} | {'https://github.com/seccomp/libseccomp-golang/commit/06e7a29f36a34b8cf419aeb87b979ee508e58f9e'} |
Go | GHSA-5r2v-6gm6-vpvh | Insecure Permissions in Gogs | routes/api/v1/api.go in Gogs 0.11.86 lacks permission checks for routes: deploy keys, collaborators, and hooks. | {'CVE-2019-14544'} | 2021-05-17T16:36:54Z | 2021-05-18T17:33:58Z | CRITICAL | null | {'CWE-200'} | {'https://github.com/gogs/gogs/issues/5764', 'https://github.com/gogs/gogs/commit/c3af3ff1d0484de3bd789ee6c6e47f35d590e945', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14544'} | null | {'https://github.com/gogs/gogs/commit/c3af3ff1d0484de3bd789ee6c6e47f35d590e945'} | {'https://github.com/gogs/gogs/commit/c3af3ff1d0484de3bd789ee6c6e47f35d590e945'} |
Go | GO-2021-0061 | null | Due to unbounded alias chasing, a maliciously crafted YAML file
can cause the system to consume significant system resources. If
parsing user input, this may be used as a denial of service vector.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/go-yaml/yaml/commit/bb4e33bf68bf89cad44d386192cbed201f35b241', 'https://github.com/go-yaml/yaml/pull/375'} | null | {'https://github.com/go-yaml/yaml/commit/bb4e33bf68bf89cad44d386192cbed201f35b241'} | {'https://github.com/go-yaml/yaml/commit/bb4e33bf68bf89cad44d386192cbed201f35b241'} |
Go | GO-2021-0104 | null | Due to improper error handling, DTLS connections were not killed when certificate verification
failed, causing users who did not check the connection state to continue to use the connection.
This could allow allow an attacker which holds the ICE password, but not a valid certificate,
to bypass this restriction.
| {'CVE-2021-28681'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/advisories/GHSA-74xm-qj29-cq8p', 'https://github.com/pion/webrtc/commit/545613dcdeb5dedb01cce94175f40bcbe045df2e', 'https://github.com/pion/webrtc/pull/1709', 'https://github.com/pion/webrtc/issues/1708'} | null | {'https://github.com/pion/webrtc/commit/545613dcdeb5dedb01cce94175f40bcbe045df2e'} | {'https://github.com/pion/webrtc/commit/545613dcdeb5dedb01cce94175f40bcbe045df2e'} |
Go | GHSA-44r7-7p62-q3fr | Insecure generation of random numbers | The miekg Go DNS package before 1.1.25, as used in CoreDNS before 1.6.6 and other products, improperly generates random numbers because math/rand is used. The TXID becomes predictable, leading to response forgeries. | {'CVE-2019-19794'} | 2021-05-18T20:42:52Z | 2021-05-18T21:09:13Z | MODERATE | null | {'CWE-338', 'CWE-330'} | {'https://github.com/miekg/dns/compare/v1.1.24...v1.1.25', 'https://github.com/miekg/dns/issues/1043', 'https://github.com/miekg/dns/pull/1044', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19794', 'https://github.com/miekg/dns/commit/8ebf2e419df7857ac8919baa05248789a8ffbf33', 'https://github.com/coredns/coredns/issues/3547', 'https://github.com/coredns/coredns/issues/3519'} | null | {'https://github.com/miekg/dns/commit/8ebf2e419df7857ac8919baa05248789a8ffbf33'} | {'https://github.com/miekg/dns/commit/8ebf2e419df7857ac8919baa05248789a8ffbf33'} |
Go | GO-2021-0112 | null | Due to improper input sanitization when marshalling Go objects into BSON, a maliciously constructed
Go structure could allow an attacker to inject additional fields into a MongoDB document. Users are
affected if they use this package to handle untrusted user input.
| {'CVE-2021-20329'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/mongodb/mongo-go-driver/pull/622', 'https://github.com/mongodb/mongo-go-driver/commit/2aca31d5986a9e1c65a92264736de9fdc3b9b4ca', 'https://github.com/advisories/GHSA-f6mq-5m25-4r72', 'https://jira.mongodb.org/browse/GODRIVER-1923'} | null | {'https://github.com/mongodb/mongo-go-driver/commit/2aca31d5986a9e1c65a92264736de9fdc3b9b4ca'} | {'https://github.com/mongodb/mongo-go-driver/commit/2aca31d5986a9e1c65a92264736de9fdc3b9b4ca'} |
Go | GO-2021-0057 | 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-35381'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/buger/jsonparser/issues/219', 'https://github.com/buger/jsonparser/pull/221', 'https://github.com/buger/jsonparser/commit/df3ea76ece10095374fd1c9a22a4fb85a44efc42'} | null | {'https://github.com/buger/jsonparser/commit/df3ea76ece10095374fd1c9a22a4fb85a44efc42'} | {'https://github.com/buger/jsonparser/commit/df3ea76ece10095374fd1c9a22a4fb85a44efc42'} |
Go | GHSA-wf43-55jj-vwq8 | DNS Rebinding in etcd | DNS rebinding vulnerability found in etcd 3.3.1 and earlier. An attacker can control his DNS records to direct to localhost, and trick the browser into sending requests to localhost (or any other address). | {'CVE-2018-1099'} | 2021-05-19T22:09:57Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-350', 'CWE-20'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JX7QTIT465BQGRGNCE74RATRQLKT2QE4/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1552717', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1099', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UPGYHMSKDPW5GAMI7BEP3XQRVRLLBJKS/', 'https://github.com/coreos/etcd/commit/a7e5790c82039945639798ae9a3289fe787f5e56', 'https://github.com/coreos/etcd/issues/9353'} | null | {'https://github.com/coreos/etcd/commit/a7e5790c82039945639798ae9a3289fe787f5e56'} | {'https://github.com/coreos/etcd/commit/a7e5790c82039945639798ae9a3289fe787f5e56'} |
Go | GHSA-3p3g-vpw6-4w66 | Authentication Bypass in hydra | ### Impact
"When using client authentication method "private_key_jwt" [1], OpenId specification says the following about assertion `jti`:"
> A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties
"Hydra does not seem to check the uniqueness of this `jti` value. Here is me sending the same token request twice, hence with the same `jti` assertion, and getting two access tokens:"
```
$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \
--data-urlencode 'scope=application openid' \
--data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \
--data-urlencode 'client_assertion=eyJhb [...] jTw'
{"access_token":"zeG0NoqOtlACl8q5J6A-TIsNegQRRUzqLZaYrQtoBZQ.VR6iUcJQYp3u_j7pwvL7YtPqGhtyQe5OhnBE2KCp5pM","expires_in":3599,"scope":"application openid","token_type":"bearer"}⏎ ~$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \
--data-urlencode 'scope=application openid' \
--data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \
--data-urlencode 'client_assertion=eyJhb [...] jTw'
{"access_token":"wOYtgCLxLXlELORrwZlmeiqqMQ4kRzV-STU2_Sollas.mwlQGCZWXN7G2IoegUe1P0Vw5iGoKrkOzOaplhMSjm4","expires_in":3599,"scope":"application openid","token_type":"bearer"}
```
### Severity
"We rate the severity as medium because the following reasons make it hard to replay tokens without the patch:"
- TLS protects against MITM which makes it difficult to intercept valid tokens for replay attacks
- The expiry time of the JWT gives only a short window of opportunity where it could be replayed
### Patches
This will be patched with v1.4.0+oryOS.17
### Workarounds
Two workarounds have been identified:
- Do not allow clients to use `private_key_jwt`
- Use short expiry times for the JWTs
### Upstream
This issue will be resolved in the upstream repository https://github.com/ory/fosite | {'CVE-2020-5300'} | 2021-05-24T21:19:26Z | 2021-05-27T18:43:22Z | MODERATE | null | {'CWE-294'} | {'https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication', 'https://github.com/ory/hydra/releases/tag/v1.4.0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5300', 'https://github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3', 'https://github.com/ory/hydra/security/advisories/GHSA-3p3g-vpw6-4w66'} | null | {'https://github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3'} | {'https://github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3'} |
Go | GHSA-c3xm-pvg7-gh7r | mount destinations can be swapped via symlink-exchange to cause mounts outside the rootfs | ### Summary
runc 1.0.0-rc94 and earlier are vulnerable to a symlink exchange attack whereby
an attacker can request a seemingly-innocuous container configuration that
actually results in the host filesystem being bind-mounted into the container
(allowing for a container escape). CVE-2021-30465 has been assigned for this
issue.
An attacker must have the ability to start containers using some kind of custom
volume configuration, and while recommended container hardening mechanisms such
as LSMs (AppArmor/SELinux) and user namespaces will restrict the amount of
damage an attacker could do, they do not block this attack outright. We have a
reproducer using Kubernetes (and the below description mentions
Kubernetes-specific paths), but this is not a Kubernetes-specific issue.
The now-released [runc v1.0.0-rc95][release] contains a fix for this issue, we
recommend users update as soon as possible.
[release]: https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc95
### Details
In circumstances where a container is being started, and runc is mounting
inside a volume shared with another container (which is conducting a
symlink-exchange attack), runc can be tricked into mounting outside of the
container rootfs by swapping the target of a mount with a symlink due to a
time-of-check-to-time-of-use (TOCTTOU) flaw. This is fairly similar in style to
previous TOCTTOU attacks (and is a problem we are working on solving with
libpathrs).
However, this alone is not useful because this happens inside a mount namespace
with `MS_SLAVE` propagation applied to `/` (meaning that the mount doesn't
appear on the host -- it's only a "host-side mount" inside the container's
namespace). To exploit this, you must have additional mount entries in the
configuration that use some subpath of the mounted-over host path as a source
for a subsequent mount.
However, it turns out with some container orchestrators (such as Kubernetes --
though it is very likely that other downstream users of runc could have similar
behaviour be accessible to untrusted users), the existence of additional volume
management infrastructure allows this attack to be applied to gain access to
the host filesystem without requiring the attacker to have completely arbitrary
control over container configuration.
In the case of Kubernetes, this is exploitable by creating a symlink in a
volume to the top-level (well-known) directory where volumes are sourced from
(for instance,
`/var/lib/kubelet/pods/$MY_POD_UID/volumes/kubernetes.io~empty-dir`), and then
using that symlink as the target of a mount. The source of the mount is an
attacker controlled directory, and thus the source directory from which
subsequent mounts will occur is an attacker-controlled directory. Thus the
attacker can first place a symlink to `/` in their malicious source directory
with the name of a volume, and a subsequent mount in the container will
bind-mount `/` into the container.
Applying this attack requires the attacker to start containers with a slightly
peculiar volume configuration (though not explicitly malicious-looking such as
bind-mounting `/` into the container explicitly), and be able to run malicious
code in a container that shares volumes with said volume configuration. It
helps the attacker if the host paths used for volume management are well known,
though this is not a hard requirement.
### Patches
This has been patched in runc 1.0.0-rc95, and users should upgrade as soon as
possible. The patch itself can be found [here](https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f).
### Workarounds
There are no known workarounds for this issue.
However, users who enforce running containers with more confined security
profiles (such as reduced capabilities, not running code as root in the
container, user namespaces, AppArmor/SELinux, and seccomp) will restrict what
an attacker can do in the case of a container breakout -- we recommend users
make use of strict security profiles if possible (most notably user namespaces
-- which can massively restrict the impact a container breakout can have on the
host system).
### References
* [commit](https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f)
* [seclists public disclosure](https://www.openwall.com/lists/oss-security/2021/05/19/2)
### Credit
Thanks to Etienne Champetier for discovering and disclosing this vulnerability,
to Noah Meyerhans for writing the first draft of this patch, and to Samuel Karp
for testing it.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [our issue tracker](https://github.com/opencontainers/runc/issues).
* Email us at <security@opencontainers.org>. | {'CVE-2021-30465'} | 2021-05-21T19:34:43Z | 2021-05-25T18:44:42Z | HIGH | null | {'CWE-367', 'CWE-22'} | {'https://github.com/opencontainers/runc/security/advisories/GHSA-c3xm-pvg7-gh7r', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4HOARVIT47RULTTFWAU7XBG4WY6TDDHV/', 'https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f', 'https://security.netapp.com/advisory/ntap-20210708-0003/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/35ZW6NBZSBH5PWIT7JU4HXOXGFVDCOHH/', 'https://github.com/opencontainers/runc/releases', 'https://nvd.nist.gov/vuln/detail/CVE-2021-30465', 'https://bugzilla.opensuse.org/show_bug.cgi?id=1185405', 'http://www.openwall.com/lists/oss-security/2021/05/19/2'} | null | {'https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f'} | {'https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f'} |
Go | GHSA-4c7m-vv47-7c69 | Insecure Permissions in Gogs | In Gogs 0.11.91, MakeEmailPrimary in models/user_mail.go lacks a "not the owner of the email" check. | {'CVE-2020-14958'} | 2021-05-12T14:55:34Z | 2021-05-18T20:33:05Z | MODERATE | null | {'CWE-281'} | {'https://github.com/gogs/gogs/pull/5988', 'https://github.com/gogs/gogs/commit/82ff0c5852f29daa5f95d965fd50665581e7ea3c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-14958'} | null | {'https://github.com/gogs/gogs/commit/82ff0c5852f29daa5f95d965fd50665581e7ea3c'} | {'https://github.com/gogs/gogs/commit/82ff0c5852f29daa5f95d965fd50665581e7ea3c'} |
Go | GHSA-gp4j-w3vj-7299 | Information Exposure in RunC | RunC allowed additional container processes via 'runc exec' to be ptraced by the pid 1 of the container. This allows the main processes of the container, if running as root, to gain access to file-descriptors of these new processes during the initialization and can lead to container escapes or modification of runC state before the process is fully placed inside the container. | {'CVE-2016-9962'} | 2021-05-20T16:22:33Z | 2021-12-20T18:21:43Z | MODERATE | null | {'CWE-200'} | {'http://seclists.org/fulldisclosure/2017/Jan/29', 'http://seclists.org/fulldisclosure/2017/Jan/21', 'https://access.redhat.com/security/vulnerabilities/cve-2016-9962', 'https://security.gentoo.org/glsa/201701-34', 'https://github.com/opencontainers/runc/commit/50a19c6ff828c58e5dab13830bd3dacde268afe5', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FINGBFMIXBG6B6ZWYH3TMRP5V3PDBNXR/', 'http://www.securityfocus.com/bid/95361', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UVM7FCOQMPKOFLDTUYSS4ES76DDM56VP/', 'https://github.com/opencontainers/runc/commit/5d93fed3d27f1e2bab58bad13b180a7a81d0b378', 'http://rhn.redhat.com/errata/RHSA-2017-0127.html', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-9962', 'https://github.com/docker/docker/releases/tag/v1.12.6', 'https://nvd.nist.gov/vuln/detail/CVE-2016-9962', 'http://rhn.redhat.com/errata/RHSA-2017-0116.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WUQ3MQNEL5IBZZLMLR72Q4YDCL2SCKRK/', 'http://www.securityfocus.com/archive/1/540001/100/0/threaded', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BQAXJMMLRU7DD2IMG47SR2K4BOFFG7FZ/', 'https://bugzilla.suse.com/show_bug.cgi?id=1012568#c6', 'http://rhn.redhat.com/errata/RHSA-2017-0123.html'} | null | {'https://github.com/opencontainers/runc/commit/50a19c6ff828c58e5dab13830bd3dacde268afe5', 'https://github.com/opencontainers/runc/commit/5d93fed3d27f1e2bab58bad13b180a7a81d0b378'} | {'https://github.com/opencontainers/runc/commit/5d93fed3d27f1e2bab58bad13b180a7a81d0b378', 'https://github.com/opencontainers/runc/commit/50a19c6ff828c58e5dab13830bd3dacde268afe5'} |
Go | GHSA-v24h-pjjv-mcp6 | Denial of service in Tendermint | ### Description
**Denial of Service 1**
Tendermint 0.33.2 and earlier does not limit the number of P2P connection requests. For each p2p connection, Tendermint allocates XXX bytes. Even though this memory is garbage collected once the connection is terminated (due to duplicate IP or reaching a maximum number of inbound peers), temporary memory spikes can lead to OOM (Out-Of-Memory) exceptions.
Tendermint 0.33.3 (and 0.32.10) limits the total number of P2P incoming connection requests to to `p2p.max_num_inbound_peers + len(p2p.unconditional_peer_ids)`.
Notes:
- Tendermint does not rate limit P2P connection requests per IP (an attacker can saturate all the inbound slots);
- Tendermint does not rate limit HTTP(S) requests. If you expose any RPC endpoints to the public, please make sure to put in place some protection (https://www.nginx.com/blog/rate-limiting-nginx/). We may implement this in the future (https://github.com/tendermint/tendermint/issues/1696).
**Denial of Service 2**
Tendermint 0.33.2 and earlier does not reclaim `activeID` of a peer after it's removed in `Mempool` reactor. This does not happen all the time. It only happens when a connection fails (for any reason) before the `Peer` is created and added to all reactors. `RemovePeer` is therefore called before `AddPeer`, which leads to always growing memory (`activeIDs` map). The `activeIDs` map has a maximum size of 65535 and the node will panic if this map reaches the maximum. An attacker can create a lot of connection attempts (exploiting Denial of Service 1), which ultimately will lead to the node panicking.
Tendermint 0.33.3 (and 0.32.10) claims `activeID` for a peer in `InitPeer`, which is executed before `MConnection` is started.
Notes:
- `InitPeer` function was added to all reactors to combat a similar issue - https://github.com/tendermint/tendermint/issues/3338;
- Denial of Service 2 is independent of Denial of Service 1 and can be executed without it.
### Impact
- All full nodes (except for validators who are behind closed networks)
- Node's memory usage increases, then it panics either in the mempool or due to OOM.
### Patches
- v0.33.3
- v0.32.10
- v0.31.12
### Workarounds
No workarounds.
### References
- https://hackerone.com/reports/820317 (not disclosed yet)
- https://github.com/tendermint/tendermint/issues/3338
- https://github.com/tendermint/tendermint/issues/1696
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint)
* Email us at [security@tendermint.com](mailto:security@tendermint.com)
More information can be found [here](https://tendermint.com/security/).
### Credits
- [fudongbai](https://hackerone.com/fudongbai) for discovering and reporting Denial of Service 2
- Ethan Buchman (@ebuchman) for writing a test case for Denial of Service 2 and Tess Rinearson (@tessr) for fixing it
- Anton Kaliaev (@melekes) for fixing Denial of Service 1 | {'CVE-2020-5303'} | 2021-05-24T21:16:50Z | 2021-05-27T18:44:09Z | LOW | null | {'CWE-789', 'CWE-787'} | {'https://github.com/tendermint/tendermint/issues/3338', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5303', 'https://github.com/tendermint/tendermint/blob/master/CHANGELOG.md#denial-of-service-1', 'https://github.com/tendermint/tendermint/issues/1696', 'https://hackerone.com/reports/820317', 'https://github.com/tendermint/tendermint/commit/e2d6859afd7dba4cf97c7f7d412e7d8fc908d1cd', 'https://github.com/tendermint/tendermint/security/advisories/GHSA-v24h-pjjv-mcp6'} | null | {'https://github.com/tendermint/tendermint/commit/e2d6859afd7dba4cf97c7f7d412e7d8fc908d1cd'} | {'https://github.com/tendermint/tendermint/commit/e2d6859afd7dba4cf97c7f7d412e7d8fc908d1cd'} |
Go | GHSA-qq3j-xp49-j73f | Plugin archive directory traversal in Helm | The Helm core maintainers have identified an information disclosure
vulnerability in Helm 3.0.0-3.2.3.
### Impact
A traversal attack is possible when installing Helm plugins from a tar
archive over HTTP. It is possible for a malicious plugin author to inject a relative
path into a plugin archive, and copy a file outside of the intended directory.
Traversal Attacks are a form of a Directory Traversal that can be exploited by
extracting files from an archive. The premise of the Directory Traversal
vulnerability is that an attacker can gain access to parts of the file system
outside of the target folder in which they should reside. The attacker can
then overwrite executable files and either invoke them remotely or wait for
the system or user to call them, thus achieving Remote Command Execution on
the victim's machine. The vulnerability can also cause damage by overwriting
configuration files or other sensitive resources, and can be exploited on both
client (user) machines and servers.
https://snyk.io/research/zip-slip-vulnerability
### Patches
This issue has been fixed in Helm 3.2.4
### 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-4053'} | 2021-05-24T20:57:17Z | 2021-06-23T18:14:36Z | LOW | null | {'CWE-22'} | {'https://github.com/helm/helm/releases/tag/v3.2.4', 'https://github.com/helm/helm/pull/8317', 'https://nvd.nist.gov/vuln/detail/CVE-2020-4053', 'https://github.com/helm/helm/commit/b6bbe4f08bbb98eadd6c9cd726b08a5c639908b3', 'https://github.com/helm/helm/security/advisories/GHSA-qq3j-xp49-j73f', 'https://github.com/helm/helm/commit/0ad800ef43d3b826f31a5ad8dfbb4fe05d143688'} | null | {'https://github.com/helm/helm/commit/b6bbe4f08bbb98eadd6c9cd726b08a5c639908b3', 'https://github.com/helm/helm/commit/0ad800ef43d3b826f31a5ad8dfbb4fe05d143688'} | {'https://github.com/helm/helm/commit/b6bbe4f08bbb98eadd6c9cd726b08a5c639908b3', 'https://github.com/helm/helm/commit/0ad800ef43d3b826f31a5ad8dfbb4fe05d143688'} |
Go | GO-2021-0094 | null | Protections against directory traversal during archive extraction can be
bypassed by chaining multiple symbolic links within the archive. This allows
a malicious attacker to cause files to be created outside of the target
directory. Additionally if the attacker is able to read extracted files
they may create symbolic links to arbitary files on the system which the
unpacker has permissions to read.
| {'CVE-2020-29529'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/hashicorp/go-slug/commit/28cafc59c8da6126a3ae94dfa84181df4073454f', 'https://securitylab.github.com/advisories/GHSL-2020-262-zipslip-go-slug', 'https://github.com/hashicorp/go-slug/pull/12'} | null | {'https://github.com/hashicorp/go-slug/commit/28cafc59c8da6126a3ae94dfa84181df4073454f'} | {'https://github.com/hashicorp/go-slug/commit/28cafc59c8da6126a3ae94dfa84181df4073454f'} |
Go | GHSA-3xh2-74w9-5vxm | Integer overflow in github.com/gorilla/websocket | An integer overflow vulnerability exists with the length of websocket frames received via a websocket connection. An attacker would use this flaw to cause a denial of service attack on an HTTP Server allowing websocket connections. | {'CVE-2020-27813'} | 2021-05-18T20:56:17Z | 2021-05-18T21:08:02Z | HIGH | null | {'CWE-400', 'CWE-190'} | {'https://github.com/gorilla/websocket/pull/537', 'https://github.com/gorilla/websocket/security/advisories/GHSA-jf24-p9p9-4rjh', 'https://github.com/gorilla/websocket/commit/5b740c29263eb386f33f265561c8262522f19d37', 'https://lists.debian.org/debian-lts-announce/2021/01/msg00008.html', 'https://bugzilla.redhat.com/show_bug.cgi?id=1902111', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27813'} | null | {'https://github.com/gorilla/websocket/commit/5b740c29263eb386f33f265561c8262522f19d37'} | {'https://github.com/gorilla/websocket/commit/5b740c29263eb386f33f265561c8262522f19d37'} |
Go | GHSA-gcj7-j438-hjj2 | Smokescreen SSRF via deny list bypass | The primary use case for Smokescreen is to prevent server-side request forgery (SSRF) attacks in which external attackers leverage the behavior of applications to connect to or scan internal infrastructure.
Smokescreen also offers an option to deny access to additional (e.g., external) URLs by way of a deny list. There was an issue in Smokescreen that made it possible to bypass the deny list feature by appending a dot to the end of user-supplied URLs, or by providing input in a different letter case.
### Recommendation
Upgrade Smokescreen to version 0.0.3 or later.
### Acknowledgements
Thanks to [Grzegorz Niedziela](https://twitter.com/gregxsunday) for reporting the issue.
### For more information
Email us at security@stripe.com | {'CVE-2022-24825'} | 2022-04-07T22:10:22Z | 2022-04-07T22:10:22Z | MODERATE | null | {'CWE-918'} | {'github.com/stripe/smokescreen', 'https://github.com/stripe/smokescreen/security/advisories/GHSA-gcj7-j438-hjj2', 'https://github.com/stripe/smokescreen/commit/fafb6ae48c6c40aa011d87b61306abc48db8797b', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24825'} | null | {'https://github.com/stripe/smokescreen/commit/fafb6ae48c6c40aa011d87b61306abc48db8797b'} | {'https://github.com/stripe/smokescreen/commit/fafb6ae48c6c40aa011d87b61306abc48db8797b'} |
Go | GHSA-7638-r9r3-rmjj | chroot isolation: environment value leakage to intermediate processes | ### Impact
When running processes using "chroot" isolation, the process being run can examine the environment variables of its immediate parent and grandparent processes (CVE-2021-3602). This isolation type is often used when running `buildah` in unprivileged containers, and it is often used to do so in CI/CD environments. If sensitive information is exposed to the original `buildah` process through its environment, that information will unintentionally be shared with child processes which it starts as part of handling RUN instructions or during `buildah run`. The commands that `buildah` is instructed to run can read that information if they choose to.
### Patches
Users should upgrade packages, or images which contain packages, to include version 1.21.3 or later.
### Workarounds
As a workaround, invoking `buildah` in a container under `env -i` to have it started with a reinitialized environment should prevent the leakage.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [buildah](https://github.com/containers/buildah/issues)
* Email us at [the buildah general mailing list](mailto:buildah@lists.buildah.io), or [the podman security mailing list](mailto:security@lists.podman.io) if it's sensitive. | {'CVE-2021-3602'} | 2022-03-18T21:03:34Z | 2021-07-19T15:19:09Z | MODERATE | null | {'CWE-200'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=1969264', 'https://ubuntu.com/security/CVE-2021-3602', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3602', 'https://github.com/containers/buildah/security/advisories/GHSA-7638-r9r3-rmjj', 'https://github.com/containers/buildah', 'https://github.com/containers/buildah/commit/a468ce0ffd347035d53ee0e26c205ef604097fb0'} | null | {'https://github.com/containers/buildah/commit/a468ce0ffd347035d53ee0e26c205ef604097fb0'} | {'https://github.com/containers/buildah/commit/a468ce0ffd347035d53ee0e26c205ef604097fb0'} |
Go | GHSA-pmcr-2rhp-36hr | SQL injection in github.com/navidrome/navidrome | model/criteria/criteria.go in Navidrome before 0.47.5 is vulnerable to SQL injection attacks when processing crafted Smart Playlists. An authenticated user could abuse this to extract arbitrary data from the database, including the user table (which contains sensitive information such as the users' encrypted passwords). | {'CVE-2022-23857'} | 2022-01-25T21:03:46Z | 2022-01-27T16:23:02Z | MODERATE | null | {'CWE-89'} | {'https://github.com/navidrome/navidrome/commit/9e79b5cbf2a48c1e4344df00fea4ed3844ea965d', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23857', 'https://github.com/navidrome/navidrome/releases/tag/v0.47.5', 'https://github.com/navidrome/navidrome'} | null | {'https://github.com/navidrome/navidrome/commit/9e79b5cbf2a48c1e4344df00fea4ed3844ea965d'} | {'https://github.com/navidrome/navidrome/commit/9e79b5cbf2a48c1e4344df00fea4ed3844ea965d'} |
Go | GHSA-8fvr-5rqf-3wwh | Information Exposure in Docker Engine | Docker Engine before 1.6.1 uses weak permissions for (1) /proc/asound, (2) /proc/timer_stats, (3) /proc/latency_stats, and (4) /proc/fs, which allows local users to modify the host, obtain sensitive information, and perform protocol downgrade attacks via a crafted image. | {'CVE-2015-3630'} | 2021-05-19T22:47:32Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-285'} | {'https://groups.google.com/forum/#%21searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-3630', 'https://lists.opensuse.org/opensuse-updates/2015-05/msg00023.html', 'https://nvd.nist.gov/vuln/detail/CVE-2015-3630', 'https://groups.google.com/forum/#!searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'https://seclists.org/fulldisclosure/2015/May/28', 'https://packetstormsecurity.com/files/131835/Docker-Privilege-Escalation-Information-Disclosure.html', 'https://github.com/moby/moby/commit/545b440a80f676a506e5837678dd4c4f65e78660', 'https://www.securityfocus.com/bid/74566'} | null | {'https://github.com/moby/moby/commit/545b440a80f676a506e5837678dd4c4f65e78660'} | {'https://github.com/moby/moby/commit/545b440a80f676a506e5837678dd4c4f65e78660'} |
Go | GHSA-7p8f-8hjm-wm92 | Lookup operations do not take into account wildcards in SpiceDB | ### Impact
Any user making use of a wildcard relationship under the right hand branch of an `exclusion` or within an `intersection` operation will see `Lookup`/`LookupResources` return a resource as "accessible" if it is *not* accessible by virtue of the inclusion of the wildcard in the intersection or the right side of the exclusion.
For example, given schema:
```zed
definition user {}
definition resource {
relation viewer: user
relation banned: user | user:*
permission view = viewer - banned
}
```
If `user:*` is placed into the `banned` relation for a particular resource, `view` should return false for *all* resources. in `v1.3.0`, the wildcard is ignored entirely in lookup's dispatch, resulting in the `banned` wildcard being ignored in the exclusion.
### Workarounds
Don't make use of wildcards on the right side of intersections or within exclusions.
### References
https://github.com/authzed/spicedb/issues/358
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [SpiceDB](https://github.com/authzed/spicedb)
* Ask a question in the [SpiceDB Discord](https://authzed.com/discord)
| {'CVE-2022-21646'} | 2022-01-13T15:02:31Z | 2022-01-13T15:05:41Z | HIGH | null | {'CWE-155', 'CWE-20'} | {'https://github.com/authzed/spicedb/commit/15bba2e2d2a4bda336a37a7fe8ef8a35028cd970', 'https://github.com/authzed/spicedb/issues/358', 'https://github.com/authzed/spicedb/releases/tag/v1.4.0', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21646', 'https://github.com/authzed/spicedb', 'https://github.com/authzed/spicedb/security/advisories/GHSA-7p8f-8hjm-wm92'} | null | {'https://github.com/authzed/spicedb/commit/15bba2e2d2a4bda336a37a7fe8ef8a35028cd970'} | {'https://github.com/authzed/spicedb/commit/15bba2e2d2a4bda336a37a7fe8ef8a35028cd970'} |
Go | GHSA-4hq8-gmxx-h6w9 | XML Processing error in github.com/crewjam/saml | ### Impact
There are three vulnerabilities in the go `encoding/xml` package that can allow an attacker to forge part of a signed XML document. For details on this vulnerability see [xml-roundtrip-validator](https://github.com/mattermost/xml-roundtrip-validator)
### Patches
In version 0.4.3, all XML input is validated prior to being parsed. | {'CVE-2020-27846'} | 2021-05-21T20:54:26Z | 2021-06-23T17:29:42Z | HIGH | null | {'CWE-115', 'CWE-287'} | {'https://security.netapp.com/advisory/ntap-20210205-0002/', 'https://github.com/crewjam/saml/security/advisories/GHSA-4hq8-gmxx-h6w9', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27846', 'https://github.com/crewjam/saml/commit/da4f1a0612c0a8dd0452cf8b3c7a6518f6b4d053', 'https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3YUTKIRWT6TWU7DS6GF3EOANVQBFQZYI/', 'https://grafana.com/blog/2020/12/17/grafana-6.7.5-7.2.3-and-7.3.6-released-with-important-security-fix-for-grafana-enterprise/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1907670', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ICP3YRY2VUCNCF2VFUSK77ZMRIC77FEM/'} | null | {'https://github.com/crewjam/saml/commit/da4f1a0612c0a8dd0452cf8b3c7a6518f6b4d053'} | {'https://github.com/crewjam/saml/commit/da4f1a0612c0a8dd0452cf8b3c7a6518f6b4d053'} |
Go | GHSA-742w-89gc-8m9c | containerd v1.2.x can be coerced into leaking credentials during image pull | ## Impact
If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers.
If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user's username and password for the registry. In other cases, this may be the credentials attached to the cloud virtual instance which can grant access to other cloud resources in the account.
The default containerd resolver is used by the cri-containerd plugin (which can be used by Kubernetes), the ctr development tool, and other client programs that have explicitly linked against it.
This vulnerability has been rated by the containerd maintainers as medium, with a CVSS score of 6.1 and a vector string of CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N.
## Patches
This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected.
## Workarounds
If you are using containerd 1.3 or later, you are not affected. If you are using cri-containerd in the 1.2 series or prior, you should ensure you only pull images from trusted sources. Other container runtimes built on top of containerd but not using the default resolver (such as Docker) are not affected.
## Credits
The containerd maintainers would like to thank Brad Geesaman, Josh Larsen, Ian Coldwater, Duffie Cooley, and Rory McCune for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/master/SECURITY.md). | {'CVE-2020-15157'} | 2022-02-11T23:27:39Z | 2022-02-11T23:27:39Z | MODERATE | null | {'CWE-522'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15157', 'https://github.com/containerd/containerd', 'https://github.com/containerd/containerd/commit/1ead8d9deb3b175bf40413b8c47b3d19c2262726', 'https://www.debian.org/security/2021/dsa-4865', 'https://usn.ubuntu.com/4589-1/', 'https://github.com/containerd/containerd/security/advisories/GHSA-742w-89gc-8m9c', 'https://usn.ubuntu.com/4589-2/', 'https://github.com/containerd/containerd/releases/tag/v1.2.14', 'https://darkbit.io/blog/cve-2020-15157-containerdrip'} | null | {'https://github.com/containerd/containerd/commit/1ead8d9deb3b175bf40413b8c47b3d19c2262726'} | {'https://github.com/containerd/containerd/commit/1ead8d9deb3b175bf40413b8c47b3d19c2262726'} |
Go | GO-2021-0082 | null | Thirft Servers preallocate memory for the declared size of messages before
checking the actual size of the message. This allows a malicious user to
send messages that declare that they are significantly larger than they
actually are, allowing them to force the server to allocate significant
amounts of memory. This can be used as a denial of service vector.
| {'CVE-2019-11939'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://www.facebook.com/security/advisories/cve-2019-11939', 'https://github.com/facebook/fbthrift/commit/483ed864d69f307e9e3b9dadec048216100c0757'} | null | {'https://github.com/facebook/fbthrift/commit/483ed864d69f307e9e3b9dadec048216100c0757'} | {'https://github.com/facebook/fbthrift/commit/483ed864d69f307e9e3b9dadec048216100c0757'} |
Go | GO-2020-0026 | null | Due to improper path santization, archives containing relative file
paths can cause files to be written (or overwritten) outside of the
target directory.
| {'CVE-2018-1103'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://snyk.io/research/zip-slip-vulnerability', 'https://github.com/openshift/source-to-image/commit/f5cbcbc5cc6f8cc2f479a7302443bea407a700cb'} | null | {'https://github.com/openshift/source-to-image/commit/f5cbcbc5cc6f8cc2f479a7302443bea407a700cb'} | {'https://github.com/openshift/source-to-image/commit/f5cbcbc5cc6f8cc2f479a7302443bea407a700cb'} |
Go | GHSA-j77r-2fxf-5jrw | Improper path handling in kustomization files allows path traversal | The kustomize-controller enables the use of Kustomize’s functionality when applying Kubernetes declarative state onto a cluster. A malicious user can use built-in features and a specially crafted `kustomization.yaml` to expose sensitive data from the controller’s pod filesystem. In multi-tenancy deployments this can lead to privilege escalation if the controller's service account has elevated permissions.
Within the affected versions, users with write access to a Flux source are able to use built-in features to expose sensitive data from the controller’s pod filesystem using a malicious `kustomization.yaml` file.
This vulnerability was fixed in kustomize-controller v0.24.0 and included in flux2 v0.29.0 released on 2022-04-20. The changes introduce a new Kustomize file system implementation which ensures that all files being handled are contained within the Kustomization working directory, blocking references to any files that do not meet that requirement.
Automated tooling (e.g. conftest) could be employed as a workaround, as part of a user's CI/CD pipeline to ensure that their `kustomization.yaml` files conform with specific policies, blocking access to sensitive path locations. | {'CVE-2022-24877'} | 2022-05-05T21:49:51Z | 2022-05-04T18:04:07Z | CRITICAL | null | {'CWE-22'} | {'https://github.com/fluxcd/pkg/commit/0ec014baf417fd3879d366a45503a548b9267d2a', 'https://github.com/fluxcd/kustomize-controller/commit/f4528fb25d611da94e491346bea056d5c5c3611f', 'https://github.com/fluxcd/flux2/security/advisories/GHSA-j77r-2fxf-5jrw', 'github.com/fluxcd/kustomize-controller'} | null | {'https://github.com/fluxcd/kustomize-controller/commit/f4528fb25d611da94e491346bea056d5c5c3611f', 'https://github.com/fluxcd/pkg/commit/0ec014baf417fd3879d366a45503a548b9267d2a'} | {'https://github.com/fluxcd/kustomize-controller/commit/f4528fb25d611da94e491346bea056d5c5c3611f', 'https://github.com/fluxcd/pkg/commit/0ec014baf417fd3879d366a45503a548b9267d2a'} |
Go | GO-2021-0066 | null | Attempting to read a malformed .dockercfg may cause secrets to be
inappropriately logged.
| {'CVE-2020-8564'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/kubernetes/kubernetes/commit/11793434dac97a49bfed0150b56ac63e5dc34634', 'https://github.com/kubernetes/kubernetes/issues/95622', 'https://github.com/kubernetes/kubernetes/pull/94712'} | null | {'https://github.com/kubernetes/kubernetes/commit/11793434dac97a49bfed0150b56ac63e5dc34634'} | {'https://github.com/kubernetes/kubernetes/commit/11793434dac97a49bfed0150b56ac63e5dc34634'} |
Go | GHSA-crp2-qrr5-8pq7 | containerd CRI plugin: Insecure handling of image volumes | ### Impact
A bug was found in containerd where containers launched through containerd’s CRI implementation with a specially-crafted image configuration could gain access to read-only copies of arbitrary files and directories on the host. This may bypass any policy-based enforcement on container setup (including a Kubernetes Pod Security Policy) and expose potentially sensitive information. Kubernetes and crictl can both be configured to use containerd’s CRI implementation.
### Patches
This bug has been fixed in containerd 1.6.1, 1.5.10 and 1.4.13. Users should update to these versions to resolve the issue.
### Workarounds
Ensure that only trusted images are used.
### Credits
The containerd project would like to thank Felix Wilhelm of Google Project Zero for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/main/SECURITY.md).
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose)
* Email us at [security@containerd.io](mailto:security@containerd.io) | {'CVE-2022-23648'} | 2022-03-29T19:11:08Z | 2022-03-02T21:33:17Z | HIGH | null | {'CWE-200'} | {'https://github.com/containerd/containerd/releases/tag/v1.4.13', 'https://github.com/containerd/containerd', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AUDQUQBZJGBWJPMRVB6QCCCRF7O3O4PA/', 'https://github.com/containerd/containerd/commit/10f428dac7cec44c864e1b830a4623af27a9fc70', 'https://github.com/containerd/containerd/releases/tag/v1.5.10', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23648', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HFTS2EF3S7HNYSNZSEJZIJHPRU7OPUV3/', 'https://github.com/containerd/containerd/security/advisories/GHSA-crp2-qrr5-8pq7', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OCCARJ6FU4MWBTXHZNMS7NELPDBIX2VO/', 'https://www.debian.org/security/2022/dsa-5091', 'http://packetstormsecurity.com/files/166421/containerd-Image-Volume-Insecure-Handling.html', 'https://github.com/containerd/containerd/releases/tag/v1.6.1'} | null | {'https://github.com/containerd/containerd/commit/10f428dac7cec44c864e1b830a4623af27a9fc70'} | {'https://github.com/containerd/containerd/commit/10f428dac7cec44c864e1b830a4623af27a9fc70'} |
Go | GO-2021-0089 | null | Parsing malformed JSON which contain opening brackets, but not closing brackes,
leads to an infinite loop. If operating on untrusted user input this can be
used as a denial of service vector.
| {'CVE-2020-10675'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/buger/jsonparser/commit/91ac96899e492584984ded0c8f9a08f10b473717', 'https://github.com/buger/jsonparser/issues/188', 'https://github.com/buger/jsonparser/pull/192'} | null | {'https://github.com/buger/jsonparser/commit/91ac96899e492584984ded0c8f9a08f10b473717'} | {'https://github.com/buger/jsonparser/commit/91ac96899e492584984ded0c8f9a08f10b473717'} |
Go | GHSA-5qgp-p5jc-w2rm | Arbitrary Code Execution in Docker | Docker before 1.3.2 allows remote attackers to write to arbitrary files and execute arbitrary code via a (1) symlink or (2) hard link attack in an image archive in a (a) pull or (b) load operation. | {'CVE-2014-6407'} | 2021-05-20T21:03:55Z | 2022-02-15T00:41:12Z | HIGH | null | {'CWE-59'} | {'https://secunia.com/advisories/60241', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-6407', 'https://secunia.com/advisories/60171', 'https://lists.opensuse.org/opensuse-security-announce/2014-12/msg00009.html', 'https://docs.docker.com/v1.3/release-notes/', 'https://www.openwall.com/lists/oss-security/2014/11/24/5', 'https://nvd.nist.gov/vuln/detail/CVE-2014-6407', 'https://github.com/docker/docker/commit/3ac6394b8082d4700483d52fbfe54914be537d9e', 'https://lists.fedoraproject.org/pipermail/package-announce/2014-December/145154.html'} | null | {'https://github.com/docker/docker/commit/3ac6394b8082d4700483d52fbfe54914be537d9e'} | {'https://github.com/docker/docker/commit/3ac6394b8082d4700483d52fbfe54914be537d9e'} |
Go | GHSA-72wf-hwcq-65h9 | Cross-Site Request Forgery in Filebrowser | A Cross-Site Request Forgery (CSRF) vulnerability exists in Filebrowser < 2.18.0 that allows attackers to create a backdoor user with admin privilege and get access to the filesystem via a malicious HTML webpage that is sent to the victim. | {'CVE-2021-46398'} | 2022-02-11T16:20:19Z | 2022-02-05T00:00:31Z | HIGH | null | {'CWE-352'} | {'https://febin0x4e4a.wordpress.com/2022/01/19/critical-csrf-in-filebrowser/', 'https://systemweakness.com/critical-csrf-to-rce-in-filebrowser-865a3c34b8e7', 'https://febin0x4e4a.blogspot.com/2022/01/critical-csrf-in-filebrowser.html', 'https://github.com/filebrowser/filebrowser/', 'http://packetstormsecurity.com/files/165885/FileBrowser-2.17.2-Code-Execution-Cross-Site-Request-Forgery.html', 'https://github.com/filebrowser/filebrowser/commit/74b7cd8e81840537a8206317344f118093153e8d', 'https://nvd.nist.gov/vuln/detail/CVE-2021-46398', 'https://febinj.medium.com/critical-csrf-to-rce-in-filebrowser-865a3c34b8e7'} | null | {'https://github.com/filebrowser/filebrowser/commit/74b7cd8e81840537a8206317344f118093153e8d'} | {'https://github.com/filebrowser/filebrowser/commit/74b7cd8e81840537a8206317344f118093153e8d'} |
Go | GHSA-25xm-hr59-7c27 | Release v0.5.8 of github.com/ulikunitz/xz fixes readUvarint denial of service | ### Impact
The function readUvarint used to read the xz container format may not terminate a loop provide malicous input.
### Patches
The problem has been fixed in release v0.5.8.
### Workarounds
Limit the size of the compressed file input to a reasonable size for your use case.
### References
The standard library had recently the same issue and got the [CVE-2020-16845](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16845) allocated.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [xz](https://github.com/ulikunitz/xz/issues). | {'CVE-2021-29482'} | 2021-05-24T17:52:22Z | 2021-05-25T18:39:37Z | HIGH | null | {'CWE-835'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29482', 'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b', 'https://github.com/ulikunitz/xz/security/advisories/GHSA-25xm-hr59-7c27'} | null | {'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b'} | {'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b'} |
Go | GHSA-25xj-89g5-fm6h | Information Disclosure in HashiCorp Vault | HashiCorp Vault and Vault Enterprise before 1.3.6, and 1.4.2 before 1.4.2, insert Sensitive Information into a Log File. | {'CVE-2020-13223'} | 2022-02-24T13:07:50Z | 2021-05-18T18:21:09Z | HIGH | null | {'CWE-532', 'CWE-200'} | {'https://www.hashicorp.com/blog/category/vault/', 'https://github.com/hashicorp/vault/commit/e52f34772affb69f3239b2cdf6523cb7cfd67a92', 'https://github.com/hashicorp/vault/commit/87f47c216cf1a28f4054b80cff40de8c9e00e36c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13223', 'https://github.com/hashicorp/vault', 'https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#142-may-21st-2020'} | null | {'https://github.com/hashicorp/vault/commit/87f47c216cf1a28f4054b80cff40de8c9e00e36c', 'https://github.com/hashicorp/vault/commit/e52f34772affb69f3239b2cdf6523cb7cfd67a92'} | {'https://github.com/hashicorp/vault/commit/87f47c216cf1a28f4054b80cff40de8c9e00e36c', 'https://github.com/hashicorp/vault/commit/e52f34772affb69f3239b2cdf6523cb7cfd67a92'} |
Go | GHSA-59hh-656j-3p7v | DoS via maliciously crafted p2p message | ### Impact
A vulnerable node is susceptible to crash when processing a maliciously crafted message from a peer, via the `snap/1` protocol. The crash can be triggered by sending a malicious `snap/1` `GetTrieNodes` package.
### Details
On September 21, 2021, geth-team member Gary Rong (@rjl493456442) found a way to crash the snap request handler .
By using this vulnerability, a peer connected on the `snap/1` protocol could cause a vulnerable node to crash with a `panic`.
In the `trie.TryGetNode` implementation, if the requested path is reached, the associated node will be returned. However the nilness is
not checked there.
```golang
func (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, newnode node, resolved int, err error) {
// If we reached the requested path, return the current node
if pos >= len(path) {
// Although we most probably have the original node expanded, encoding
// that into consensus form can be nasty (needs to cascade down) and
// time consuming. Instead, just pull the hash up from disk directly.
var hash hashNode
if node, ok := origNode.(hashNode); ok {
hash = node
} else {
hash, _ = origNode.cache()
}
```
More specifically the `origNode` can be nil(e.g. the child of fullnode) and system can panic at line `hash, _ = origNode.cache()`.
When investigating this, @holiman tried to find it via fuzzing, which uncovered a second crasher, also related to the snap `GetTrieNodes` package. If the caller requests a storage trie:
```golang
// Storage slots requested, open the storage trie and retrieve from there
account, err := snap.Account(common.BytesToHash(pathset[0]))
loads++ // always account database reads, even for failures
if account == nil {
break
}
stTrie, err := trie.NewSecure(common.BytesToHash(account.Root), triedb)
```
The code assumes that `snap.Account` returns _either_ a non-nil response unless `error` is also provided. This is however not the case, since `snap.Account` can return `nil, nil`.
### Patches
```diff
--- a/eth/protocols/snap/handler.go
+++ b/eth/protocols/snap/handler.go
@@ -469,7 +469,7 @@ func handleMessage(backend Backend, peer *Peer) error {
// Storage slots requested, open the storage trie and retrieve from there
account, err := snap.Account(common.BytesToHash(pathset[0]))
loads++ // always account database reads, even for failures
- if err != nil {
+ if err != nil || account == nil {
break
}
stTrie, err := trie.NewSecure(common.BytesToHash(account.Root), triedb)
diff --git a/trie/trie.go b/trie/trie.go
index 7ea7efa835..d0f0d4e2bc 100644
--- a/trie/trie.go
+++ b/trie/trie.go
@@ -174,6 +174,10 @@ func (t *Trie) TryGetNode(path []byte) ([]byte, int, error) {
}
func (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, newnode node, resolved int, err error) {
+ // If non-existent path requested, abort
+ if origNode == nil {
+ return nil, nil, 0, nil
+ }
// If we reached the requested path, return the current node
if pos >= len(path) {
// Although we most probably have the original node expanded, encoding
@@ -193,10 +197,6 @@ func (t *Trie) tryGetNode(origNode node, path []byte, pos int) (item []byte, new
}
// Path still needs to be traversed, descend into children
switch n := (origNode).(type) {
- case nil:
- // Non-existent path requested, abort
- return nil, nil, 0, nil
-
case valueNode:
// Path prematurely ended, abort
return nil, nil, 0, nil
```
The fixes were merged into [#23657](https://github.com/ethereum/go-ethereum/pull/23657), with commit [f1fd963](https://github.com/ethereum/go-ethereum/pull/23657/commits/f1fd963a5a965e643e52fcf805a2a02a323c32b8), and released as part of Geth [v1.10.9](https://github.com/ethereum/go-ethereum/tree/v1.10.9) on Sept 29, 2021.
### Workarounds
Apply the patch above or upgrade to a version which is not vulnerable.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum/)
* Email us at [security@ethereum.org](mailto:security@ethereum.org)
| {'CVE-2021-41173'} | 2021-11-23T19:17:38Z | 2021-10-25T19:42:57Z | MODERATE | null | {'CWE-20'} | {'https://github.com/ethereum/go-ethereum', 'https://github.com/ethereum/go-ethereum/pull/23801', 'https://github.com/ethereum/go-ethereum/commit/e40b37718326b8b4873b3b00a0db2e6c6d9ea738', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41173', 'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-59hh-656j-3p7v', 'https://github.com/ethereum/go-ethereum/releases/tag/v1.10.9'} | null | {'https://github.com/ethereum/go-ethereum/commit/e40b37718326b8b4873b3b00a0db2e6c6d9ea738'} | {'https://github.com/ethereum/go-ethereum/commit/e40b37718326b8b4873b3b00a0db2e6c6d9ea738'} |
Go | GO-2021-0070 | null | GetExecUser in the github.com/opencontainers/runc/libcontainer/user package will
improperly interpred numeric UIDs as usernames. If the method is used without
verify usernames are formatted as expected, it may allow a user to gain unexpected
privileges.
| {'CVE-2016-3697'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'http://rhn.redhat.com/errata/RHSA-2016-1034.html', 'https://github.com/docker/docker/issues/21436', 'https://github.com/opencontainers/runc/commit/69af385de62ea68e2e608335cffbb0f4aa3db091', 'https://github.com/opencontainers/runc/pull/708', 'https://security.gentoo.org/glsa/201612-28', 'http://rhn.redhat.com/errata/RHSA-2016-2634.html'} | null | {'https://github.com/opencontainers/runc/commit/69af385de62ea68e2e608335cffbb0f4aa3db091'} | {'https://github.com/opencontainers/runc/commit/69af385de62ea68e2e608335cffbb0f4aa3db091'} |
Go | GHSA-m9hp-7r99-94h5 | Critical security issues in XML encoding in github.com/dexidp/dex | ### Impact
The following vulnerabilities have been disclosed, which impact users leveraging the SAML connector:
Signature Validation Bypass (CVE-2020-15216): https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7
`encoding/xml` instabilities:
- [Element namespace prefix instability (CVE-2020-29511)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-elements.md)
- [Attribute namespace prefix instability (CVE-2020-29509)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-attributes.md)
- [Directive comment instability (CVE-2020-29510)](https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-directives.md)
### Patches
Immediately update to [Dex v2.27.0](https://github.com/dexidp/dex/releases/tag/v2.27.0).
### Workarounds
There are no known workarounds. | {'CVE-2020-26290'} | 2021-05-21T20:49:36Z | 2021-12-20T17:53:53Z | CRITICAL | null | {'CWE-347'} | {'https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-attributes.md', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26290', 'https://github.com/dexidp/dex/security/advisories/GHSA-m9hp-7r99-94h5', 'https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7', 'https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/', 'https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-elements.md', 'https://github.com/mattermost/xml-roundtrip-validator/blob/master/advisories/unstable-directives.md', 'https://github.com/dexidp/dex/releases/tag/v2.27.0', 'https://github.com/dexidp/dex/commit/324b1c886b407594196113a3dbddebe38eecd4e8'} | null | {'https://github.com/dexidp/dex/commit/324b1c886b407594196113a3dbddebe38eecd4e8'} | {'https://github.com/dexidp/dex/commit/324b1c886b407594196113a3dbddebe38eecd4e8'} |
Go | GHSA-mj9r-wwm8-7q52 | Open Redirect in github.com/AndrewBurian/powermux | ### Impact
Attackers may be able to craft phishing links and other open redirects by exploiting the trailing slash redirection feature. This may lead to users being redirected to untrusted sites after following an attacker crafted link.
### Patches
The issue is resolved in v1.1.1
### Workarounds
There are no existing workarounds.
You may detect attempts to craft urls that exploit this feature by looking for request paths containing pairs of forward slashes in sequence combined with a trailing slash e.g. `https://example.com//foo/`
| {'CVE-2021-32721'} | 2021-06-30T17:43:53Z | 2021-07-01T17:00:32Z | MODERATE | null | {'CWE-601'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32721', 'https://github.com/AndrewBurian/powermux/commit/5e60a8a0372b35a898796c2697c40e8daabed8e9', 'https://github.com/AndrewBurian/powermux/security/advisories/GHSA-mj9r-wwm8-7q52'} | null | {'https://github.com/AndrewBurian/powermux/commit/5e60a8a0372b35a898796c2697c40e8daabed8e9'} | {'https://github.com/AndrewBurian/powermux/commit/5e60a8a0372b35a898796c2697c40e8daabed8e9'} |
Go | GHSA-w3jx-wv97-67ph | Cross-site scripting in Dutchcoders transfer.sh | Dutchcoders transfer.sh before 1.2.4 allows XSS via an inline view. | {'CVE-2021-33496'} | 2021-05-28T18:03:43Z | 2021-06-29T21:25:27Z | MODERATE | null | {'CWE-79'} | {'https://vuln.ryotak.me/advisories/43', 'https://github.com/dutchcoders/transfer.sh/pull/373', 'https://github.com/dutchcoders/transfer.sh/releases/tag/v1.2.4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-33496', 'https://github.com/dutchcoders/transfer.sh/commit/9df18fdc69de2e71f30d8c1e6bfab2fda2e52eb4'} | null | {'https://github.com/dutchcoders/transfer.sh/commit/9df18fdc69de2e71f30d8c1e6bfab2fda2e52eb4'} | {'https://github.com/dutchcoders/transfer.sh/commit/9df18fdc69de2e71f30d8c1e6bfab2fda2e52eb4'} |
Go | GHSA-jpj5-hg26-6jgc | Cross-site Scripting in Alist | Alist versions 2.0.10 through 2.1.0 were discovered to contain a cross-site scripting (XSS) vulnerability via /i/:data/ipa.plist. This issue was fixed in version 2.1.1. | {'CVE-2022-26533'} | 2022-03-23T15:47:27Z | 2022-03-13T00:00:54Z | MODERATE | null | {'CWE-79'} | {'https://github.com/Xhofe/alist', 'https://github.com/Xhofe/alist/issues/645', 'https://nvd.nist.gov/vuln/detail/CVE-2022-26533', 'https://github.com/Xhofe/alist/commit/6af17e2509a400979420f613fd7f2f9721fdcd6e'} | null | {'https://github.com/Xhofe/alist/commit/6af17e2509a400979420f613fd7f2f9721fdcd6e'} | {'https://github.com/Xhofe/alist/commit/6af17e2509a400979420f613fd7f2f9721fdcd6e'} |
Go | GO-2020-0017 | null | If a JWT contains an audience claim with an array of strings, rather
than a single string, and `MapClaims.VerifyAudience` is called with
`req` set to `false`, then audience verification will be bypassed,
allowing an invalid set of audiences to be provided.
| {'CVE-2020-26160'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/dgrijalva/jwt-go/issues/422', 'https://github.com/dgrijalva/jwt-go/commit/ec0a89a131e3e8567adcb21254a5cd20a70ea4ab'} | null | {'https://github.com/dgrijalva/jwt-go/commit/ec0a89a131e3e8567adcb21254a5cd20a70ea4ab'} | {'https://github.com/dgrijalva/jwt-go/commit/ec0a89a131e3e8567adcb21254a5cd20a70ea4ab'} |
Go | GHSA-g5v4-5x39-vwhx | Zip slip directory exploit in github.com/deislabs/oras | ### Impact
The directory support (#55) allows the downloaded gzipped tarballs to be automatically extracted to the user-specified directory where the tarball can have symbolic links and hard links.
A well-crafted tarball or tarballs allow malicious artifact providers linking, writing, or overwriting specific files on the host filesystem outside of the user-specified directory unexpectedly with the same permissions as the user who runs `oras pull`.
Precisely, the following users of the affected versions are impacted
- `oras` CLI users who runs `oras pull`.
- Go programs, which invokes `github.com/deislabs/oras/pkg/content.FileStore`.
### Patches
The problem has been patched by the PR linked with this advisory. Users should upgrade their `oras` CLI and packages to `0.9.0`.
### Workarounds
For `oras` CLI users, there is no workarounds other than pulling from a trusted artifact provider.
For `oras` package users, the workaround is to not use `github.com/deislabs/oras/pkg/content.FileStore`, and use other content stores instead, or pull from a trusted artifact provider.
### References
- [Zip Slip](https://github.com/snyk/zip-slip-vulnerability)
### For more information
If you have any questions or comments about this advisory:
* Open an issue on the [GitHub repo](https://github.com/deislabs/oras)
* Email the [list of maintainers](https://github.com/deislabs/oras/blob/main/MAINTAINERS) | {'CVE-2021-21272'} | 2022-02-15T00:32:04Z | 2022-02-15T00:32:04Z | HIGH | null | {'CWE-29', 'CWE-22'} | {'https://github.com/deislabs/oras/commit/96cd90423303f1bb42bd043cb4c36085e6e91e8e', 'https://pkg.go.dev/github.com/deislabs/oras/pkg/oras', 'https://github.com/deislabs/oras/security/advisories/GHSA-g5v4-5x39-vwhx', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21272', 'https://github.com/deislabs/oras/releases/tag/v0.9.0'} | null | {'https://github.com/deislabs/oras/commit/96cd90423303f1bb42bd043cb4c36085e6e91e8e'} | {'https://github.com/deislabs/oras/commit/96cd90423303f1bb42bd043cb4c36085e6e91e8e'} |
Go | GO-2020-0001 | null | The default [`Formatter`][LoggerConfig.Formatter] for the [`Logger`][] middleware
(included in the [`Default`][] engine) allows attackers to inject arbitrary log
entries by manipulating the request path.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/gin-gonic/gin/pull/2237', 'https://github.com/gin-gonic/gin/commit/a71af9c144f9579f6dbe945341c1df37aaf09c0d'} | null | {'https://github.com/gin-gonic/gin/commit/a71af9c144f9579f6dbe945341c1df37aaf09c0d'} | {'https://github.com/gin-gonic/gin/commit/a71af9c144f9579f6dbe945341c1df37aaf09c0d'} |
Go | GO-2020-0021 | null | Due to improper santization of user input, a number of methods are
vulnerable to SQL injection if used with user input that has not
been santized by the caller.
| {'CVE-2014-8681'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://seclists.org/fulldisclosure/2014/Nov/31', 'https://github.com/gogs/gogs/commit/83283bca4cb4e0f4ec48a28af680f0d88db3d2c8'} | null | {'https://github.com/gogs/gogs/commit/83283bca4cb4e0f4ec48a28af680f0d88db3d2c8'} | {'https://github.com/gogs/gogs/commit/83283bca4cb4e0f4ec48a28af680f0d88db3d2c8'} |
Go | GHSA-c3g4-w6cv-6v7h | Non-empty default inheritable capabilities for linux container in Buildah | A bug was found in Buildah where containers were created with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2).
This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set.
| {'CVE-2022-27651'} | 2022-04-19T18:02:46Z | 2022-04-01T13:56:42Z | MODERATE | null | {'CWE-276'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=2066840', 'https://github.com/containers/buildah/security/advisories/GHSA-c3g4-w6cv-6v7h', 'https://nvd.nist.gov/vuln/detail/CVE-2022-27651', 'https://github.com/containers/buildah', 'https://github.com/containers/buildah/pull/3855', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7NETC7I6RTMMBRJJQVJOJUPDK4W4PQSJ/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2VWH6X6HOFPO6HTESF42HIJZEPXSWVIO/', 'https://github.com/containers/buildah/commit/90b3254c7404039c1c786999ac189654228f6e0e', 'https://github.com/containers/buildah/commit/e7e55c988c05dd74005184ceb64f097a0cfe645b'} | null | {'https://github.com/containers/buildah/commit/90b3254c7404039c1c786999ac189654228f6e0e', 'https://github.com/containers/buildah/commit/e7e55c988c05dd74005184ceb64f097a0cfe645b'} | {'https://github.com/containers/buildah/commit/90b3254c7404039c1c786999ac189654228f6e0e', 'https://github.com/containers/buildah/commit/e7e55c988c05dd74005184ceb64f097a0cfe645b'} |
Go | GO-2021-0085 | null | AppArmor restrictions may be bypassed due to improper validation of mount
targets, allowing a malicious image to mount volumes over e.g. /proc.
| {'CVE-2019-16884'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/opencontainers/runc/issues/2128', 'https://github.com/opencontainers/runc/commit/cad42f6e0932db0ce08c3a3d9e89e6063ec283e4', 'https://github.com/opencontainers/runc/pull/2130'} | null | {'https://github.com/opencontainers/runc/commit/cad42f6e0932db0ce08c3a3d9e89e6063ec283e4'} | {'https://github.com/opencontainers/runc/commit/cad42f6e0932db0ce08c3a3d9e89e6063ec283e4'} |
Go | GHSA-9689-rx4v-cqgc | Open Redirect | Pivotal Concourse Release, versions 4.x prior to 4.2.2, login flow allows redirects to untrusted websites. A remote unauthenticated attacker could convince a user to click on a link using the oAuth redirect link with an untrusted website and gain access to that user's access token in Concourse. | {'CVE-2018-15798'} | 2021-05-12T18:15:16Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-601'} | {'https://github.com/concourse/concourse/blob/release/5.2.x/release-notes/v5.2.8.md', 'https://pivotal.io/security/cve-2018-15798', 'https://nvd.nist.gov/vuln/detail/CVE-2018-15798', 'https://github.com/concourse/concourse/pull/5350/commits/38cb4cc025e5ed28764b4adc363a0bbf41f3c7cb'} | null | {'https://github.com/concourse/concourse/pull/5350/commits/38cb4cc025e5ed28764b4adc363a0bbf41f3c7cb'} | {'https://github.com/concourse/concourse/pull/5350/commits/38cb4cc025e5ed28764b4adc363a0bbf41f3c7cb'} |
Go | GHSA-5gjh-5j4f-cpwv | Unrestricted Upload of File with Dangerous Type in Gogs | ### Impact
The malicious user is able to upload a crafted `config` file into repository's `.git` directory with to gain SSH access to the server. All installations with [repository upload enabled (default)](https://github.com/gogs/gogs/blob/f36eeedbf89328ee70cc3a2e239f6314f9021f58/conf/app.ini#L127-L129) are affected.
### Patches
Repository file uploads are prohibited to its `.git` directory. Users should upgrade to 0.12.6 or the latest 0.13.0+dev.
### Workarounds
[Disable repository files upload](https://github.com/gogs/gogs/blob/f36eeedbf89328ee70cc3a2e239f6314f9021f58/conf/app.ini#L128-L129).
### References
https://huntr.dev/bounties/b4928cfe-4110-462f-a180-6d5673797902/
### For more information
If you have any questions or comments about this advisory, please post on #6833.
| {'CVE-2022-0415'} | 2022-03-28T16:46:41Z | 2022-03-28T16:46:41Z | HIGH | null | {'CWE-434', 'CWE-20'} | {'https://github.com/gogs/gogs/commit/0fef3c9082269e9a4e817274942a5d7c50617284', 'https://huntr.dev/bounties/b4928cfe-4110-462f-a180-6d5673797902', 'https://github.com/gogs/gogs/security/advisories/GHSA-5gjh-5j4f-cpwv', 'https://github.com/gogs/gogs/pull/6838', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0415', 'https://github.com/gogs/gogs/issues/6833', 'https://github.com/gogs/gogs'} | null | {'https://github.com/gogs/gogs/commit/0fef3c9082269e9a4e817274942a5d7c50617284'} | {'https://github.com/gogs/gogs/commit/0fef3c9082269e9a4e817274942a5d7c50617284'} |
Go | GHSA-fgv8-vj5c-2ppq | Incorrect Authorization in runc | runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount targets, and thus a malicious Docker image can mount over a /proc directory. | {'CVE-2019-16884'} | 2022-02-22T15:38:08Z | 2022-02-22T15:38:08Z | HIGH | null | {'CWE-863'} | {'https://access.redhat.com/errata/RHSA-2019:4269', 'http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00073.html', 'http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00009.html', 'https://github.com/opencontainers/runc/pull/2129', 'https://github.com/crosbymichael/runc/commit/78dce1cf1ec36bbe7fe6767bdb81f7cbf6d34d70', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/62OQ2P7K5YDZ5BRCH2Q6DHUJIHQD3QCD/', 'https://usn.ubuntu.com/4297-1/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SPK4JWP32BUIVDJ3YODZSOEVEW6BHQCF/', 'https://github.com/opencontainers/runc/issues/2128', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DGK6IV5JGVDXHOXEKJOJWKOVNZLT6MYR/', 'https://access.redhat.com/errata/RHSA-2019:4074', 'https://security.netapp.com/advisory/ntap-20220221-0004/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16884', 'https://access.redhat.com/errata/RHSA-2019:3940', 'http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00010.html', 'https://security.gentoo.org/glsa/202003-21'} | null | {'https://github.com/crosbymichael/runc/commit/78dce1cf1ec36bbe7fe6767bdb81f7cbf6d34d70'} | {'https://github.com/crosbymichael/runc/commit/78dce1cf1ec36bbe7fe6767bdb81f7cbf6d34d70'} |
Go | GHSA-qvf8-p83w-v58j | Podman's default inheritable capabilities for linux container not empty | A bug was found in Podman where containers were created with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2).
This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. | {'CVE-2022-27649'} | 2022-04-19T18:03:15Z | 2022-04-01T20:52:29Z | HIGH | null | {'CWE-276'} | {'https://github.com/containers/podman/releases/tag/v4.0.3', 'https://bugzilla.redhat.com/show_bug.cgi?id=2066568', 'https://github.com/containers/podman/security/advisories/GHSA-qvf8-p83w-v58j', 'https://github.com/containers/podman/commit/aafa80918a245edcbdaceb1191d749570f1872d0', 'https://github.com/containers/podman', 'https://nvd.nist.gov/vuln/detail/CVE-2022-27649', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/J5WPM42UR6XIBQNQPNQHM32X7S4LJTRX/'} | null | {'https://github.com/containers/podman/commit/aafa80918a245edcbdaceb1191d749570f1872d0'} | {'https://github.com/containers/podman/commit/aafa80918a245edcbdaceb1191d749570f1872d0'} |
Go | GO-2020-0037 | null | Due to support of Gzip compression in request bodies, as well
as a lack of limiting response body sizes, a malicious server
can cause a client to consume a significant amount of system
resources, which may be used as a denial of service vector.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/tendermint/tendermint/pull/3430', 'https://github.com/tendermint/tendermint/commit/03085c2da23b179c4a51f59a03cb40aa4e85a613'} | null | {'https://github.com/tendermint/tendermint/commit/03085c2da23b179c4a51f59a03cb40aa4e85a613'} | {'https://github.com/tendermint/tendermint/commit/03085c2da23b179c4a51f59a03cb40aa4e85a613'} |
Go | GHSA-26cm-qrc6-mfgj | Improper Neutralization of Special Elements used in an LDAP Query in stevenweathers/thunderdome-planning-poker | ### Impact
LDAP injection vulnerability, only affects instances with LDAP authentication enabled.
### Patches
Patch for vulnerability released with v1.16.3.
### Workarounds
Disable LDAP feature if in use
### References
[OWASP LDAP Injection Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/LDAP_Injection_Prevention_Cheat_Sheet.html
)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Thunderdome Github Repository](https://github.com/StevenWeathers/thunderdome-planning-poker)
* Email us at [steven@weathers.me](mailto:steven@weathers.me)
| {'CVE-2021-41232'} | 2021-11-02T18:40:07Z | 2021-11-08T18:16:21Z | HIGH | null | {'CWE-90', 'CWE-74'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41232', 'https://github.com/StevenWeathers/thunderdome-planning-poker/commit/f1524d01e8a0f2d6c3db5461c742456c692dd8c1', 'https://github.com/github/securitylab/issues/464#issuecomment-957094994', 'https://github.com/StevenWeathers/thunderdome-planning-poker', 'https://github.com/StevenWeathers/thunderdome-planning-poker/security/advisories/GHSA-26cm-qrc6-mfgj'} | null | {'https://github.com/StevenWeathers/thunderdome-planning-poker/commit/f1524d01e8a0f2d6c3db5461c742456c692dd8c1'} | {'https://github.com/StevenWeathers/thunderdome-planning-poker/commit/f1524d01e8a0f2d6c3db5461c742456c692dd8c1'} |
Go | GHSA-q2qr-3c2p-9235 | Denial of Service (DoS) in HashiCorp Consul | HashiCorp Consul and Consul Enterprise could crash when configured with an abnormally-formed service-router entry. Introduced in 1.6.0, fixed in 1.6.6 and 1.7.4. | {'CVE-2020-12758'} | 2021-05-13T14:26:25Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-400'} | {'https://github.com/hashicorp/consul/blob/v1.7.4/CHANGELOG.md', 'https://github.com/hashicorp/consul/pull/7783', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12758', 'https://github.com/hashicorp/consul/blob/v1.6.6/CHANGELOG.md', 'https://github.com/hashicorp/consul/commit/69b44fb9424cfdc05f1b7243876ab10d236ef1fc'} | null | {'https://github.com/hashicorp/consul/commit/69b44fb9424cfdc05f1b7243876ab10d236ef1fc'} | {'https://github.com/hashicorp/consul/commit/69b44fb9424cfdc05f1b7243876ab10d236ef1fc'} |
Go | GHSA-jm5c-rv3w-w83m | Denial of service in geth | ### Impact
Denial-of-service (crash) during block processing
### Details
Affected versions suffer from a vulnerability which can be exploited through the `MULMOD` operation, by specifying a modulo of `0`: `mulmod(a,b,0)`, causing a `panic` in the underlying library.
The crash was in the `uint256` library, where a buffer [underflowed](https://github.com/holiman/uint256/blob/4ce82e695c10ddad57215bdbeafb68b8c5df2c30/uint256.go#L442).
if `d == 0`, `dLen` remains `0`
and https://github.com/holiman/uint256/blob/4ce82e695c10ddad57215bdbeafb68b8c5df2c30/uint256.go#L451 will try to access index `[-1]`.
The `uint256` library was first merged in this [commit](https://github.com/ethereum/go-ethereum/commit/cf6674539c589f80031f3371a71c6a80addbe454), on 2020-06-08.
Exploiting this vulnerabilty would cause all vulnerable nodes to drop off the network.
The issue was brought to our attention through a [bug report](https://github.com/ethereum/go-ethereum/issues/21367), showing a `panic` occurring on sync from genesis on the Ropsten network.
It was estimated that the least obvious way to fix this would be to merge the fix into `uint256`, make a new release of that library and then update the geth-dependency.
- https://github.com/holiman/uint256/releases/tag/v1.1.1 was made the same day,
- PR to address the issue: https://github.com/holiman/uint256/pull/80
- PR to update geth deps: https://github.com/ethereum/go-ethereum/pull/21368
### Patches
Upgrade to v1.9.18 or higher
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)
* Email us at [security@ethereum.org](mailto:security@ethereum.org) | {'CVE-2020-26242'} | 2021-05-21T21:50:44Z | 2021-06-29T21:13:20Z | MODERATE | null | {'CWE-125', 'CWE-400', 'CWE-191'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-26242', 'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-jm5c-rv3w-w83m', 'https://blog.ethereum.org/2020/11/12/geth_security_release/', 'https://github.com/ethereum/go-ethereum/commit/7163a6664ee664df81b9028ab3ba13b9d65a7196'} | null | {'https://github.com/ethereum/go-ethereum/commit/7163a6664ee664df81b9028ab3ba13b9d65a7196'} | {'https://github.com/ethereum/go-ethereum/commit/7163a6664ee664df81b9028ab3ba13b9d65a7196'} |
Go | GHSA-34jx-wx69-9x8v | Symlink Attack in kubectl cp | The kubectl cp command allows copying files between containers and the user machine. To copy files from a container, Kubernetes creates a tar inside the container, copies it over the network, and kubectl unpacks it on the user’s machine. If the tar binary in the container is malicious, it could run any code and output unexpected, malicious results. An attacker could use this to write files to any path on the user’s machine when kubectl cp is called, limited only by the system permissions of the local user. The untar function can both create and follow symbolic links. The issue is resolved in kubectl v1.11.9, v1.12.7, v1.13.5, and v1.14.0. | {'CVE-2019-1002101'} | 2021-05-19T21:58:27Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-59'} | {'https://access.redhat.com/errata/RHBA-2019:0636', 'http://www.securityfocus.com/bid/107652', 'https://www.twistlock.com/labs-blog/disclosing-directory-traversal-vulnerability-kubernetes-copy-cve-2019-1002101/', 'https://github.com/kubernetes/kubernetes/pull/75037', 'https://access.redhat.com/errata/RHBA-2019:0619', 'https://access.redhat.com/errata/RHBA-2019:0620', 'http://www.openwall.com/lists/oss-security/2019/06/21/1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BPV2RE5RMOGUVP5WJMXKQJZUBBLAFZPZ/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QZB7E3DOZ5WDG46XAIU6K32CXHXPXB2F/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1002101', 'https://github.com/kubernetes/kubernetes/commit/47063891dd782835170f500a83f37cc98c3c1013', 'http://www.openwall.com/lists/oss-security/2019/08/05/5'} | null | {'https://github.com/kubernetes/kubernetes/commit/47063891dd782835170f500a83f37cc98c3c1013'} | {'https://github.com/kubernetes/kubernetes/commit/47063891dd782835170f500a83f37cc98c3c1013'} |
Go | GO-2021-0103 | null | Due to improper bounds checking, certain mathmatical operations can cause a panic, due to an
out of bounds read. If this package is used to process untrusted user inputs, this may be used
as a vector for a denial of service attack.
| {'CVE-2020-26242'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/holiman/uint256/commit/6785da6e3eea403260a5760029e722aa4ff1716d', 'https://github.com/holiman/uint256/pull/80', 'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-jm5c-rv3w-w83m'} | null | {'https://github.com/holiman/uint256/commit/6785da6e3eea403260a5760029e722aa4ff1716d'} | {'https://github.com/holiman/uint256/commit/6785da6e3eea403260a5760029e722aa4ff1716d'} |
Go | GHSA-rgjg-66cx-5x9m | Authentication Bypass | Grafana before 4.6.4 and 5.x before 5.2.3 allows authentication bypass because an attacker can generate a valid "remember me" cookie knowing only a username of an LDAP or OAuth user. | {'CVE-2018-15727'} | 2021-05-20T21:09:16Z | 2022-02-15T01:57:18Z | CRITICAL | null | {'CWE-287'} | {'https://grafana.com/blog/2018/08/29/grafana-5.2.3-and-4.6.4-released-with-important-security-fix/', 'https://access.redhat.com/errata/RHSA-2019:0019', 'https://nvd.nist.gov/vuln/detail/CVE-2018-15727', 'https://www.securityfocus.com/bid/105184', 'https://access.redhat.com/errata/RHSA-2018:3829', 'https://github.com/grafana/grafana/commit/7baecf0d0deae0d865e45cf03e082bc0db3f28c3', 'https://github.com/grafana/grafana/commit/df83bf10a225811927644bdf6265fa80bdea9137'} | null | {'https://github.com/grafana/grafana/commit/7baecf0d0deae0d865e45cf03e082bc0db3f28c3', 'https://github.com/grafana/grafana/commit/df83bf10a225811927644bdf6265fa80bdea9137'} | {'https://github.com/grafana/grafana/commit/7baecf0d0deae0d865e45cf03e082bc0db3f28c3', 'https://github.com/grafana/grafana/commit/df83bf10a225811927644bdf6265fa80bdea9137'} |
Go | GHSA-j7px-6hwj-hpjg | Open Redirect in OAuth2 Proxy | ### Impact
As users can provide a redirect address for the proxy to send the authenticated user to at the end of the authentication flow. This is expected to be the original URL that the user was trying to access.
This redirect URL is checked within the proxy and validated before redirecting the user to prevent malicious actors providing redirects to potentially harmful sites.
However, by crafting a redirect URL with HTML encoded whitespace characters (eg. `%0a`, `%0b`,`%09`,`%0d`) the validation could be bypassed and allow a redirect to any URL provided.
### Patches
@rootxharsh and @iamnoooob provided this patch as potential solution:
```
From 4b941f56eda310b5c4dc8080b7635a6bfabccad4 Mon Sep 17 00:00:00 2001
From: Harsh Jaiswal <harsh@pop-os.localdomain>
Date: Fri, 1 May 2020 20:38:31 +0530
Subject: [PATCH] Fixes redirect issue
---
oauthproxy.go | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/oauthproxy.go b/oauthproxy.go
index 1e9bb7c..f8beb4d 100644
--- a/oauthproxy.go
+++ b/oauthproxy.go
@@ -577,8 +577,9 @@ func validOptionalPort(port string) bool {
// IsValidRedirect checks whether the redirect URL is whitelisted
func (p *OAuthProxy) IsValidRedirect(redirect string) bool {
+ matched, _ := regexp.MatchString(`^/\s+/|\\`, redirect)
switch {
- case strings.HasPrefix(redirect, "/") && !strings.HasPrefix(redirect, "//") && !strings.HasPrefix(redirect, "/\\"):
+ case strings.HasPrefix(redirect, "/") && !strings.HasPrefix(redirect, "//") && !matched:
return true
case strings.HasPrefix(redirect, "http://") || strings.HasPrefix(redirect, "https://"):
redirectURL, err := url.Parse(redirect)
--
2.17.1
```
This issue was also reported to us separately by @mik317 several hours later
The fix was implemented in [#xxx]() and released as version 5.1.1 | {'CVE-2020-11053'} | 2021-05-24T21:05:58Z | 2021-12-20T17:59:10Z | HIGH | null | {'CWE-601'} | {'https://github.com/oauth2-proxy/oauth2-proxy/commit/0d5fa211df8ef2449347a56b22c779eb8d894c43', 'https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-j7px-6hwj-hpjg', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11053'} | null | {'https://github.com/oauth2-proxy/oauth2-proxy/commit/0d5fa211df8ef2449347a56b22c779eb8d894c43'} | {'https://github.com/oauth2-proxy/oauth2-proxy/commit/0d5fa211df8ef2449347a56b22c779eb8d894c43'} |
Go | GO-2021-0102 | null | Due to improper input validation, a maliciously crafted input can cause a panic, due to incorrect
nonce size. If this package is used to decrypt user supplied messages without checking the size of
supplied nonces, this may be used as a vector for a denial of service attack.
| {'CVE-2019-11289'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/advisories/GHSA-5796-p3m6-9qj4', 'https://www.cloudfoundry.org/blog/cve-2019-11289/', 'https://github.com/cloudfoundry/gorouter/commit/b1b5c44e050f73b399b379ca63a42a2c5780a83f'} | null | {'https://github.com/cloudfoundry/gorouter/commit/b1b5c44e050f73b399b379ca63a42a2c5780a83f'} | {'https://github.com/cloudfoundry/gorouter/commit/b1b5c44e050f73b399b379ca63a42a2c5780a83f'} |
Go | GHSA-cpgw-2wxr-pww3 | Open Redirect | Open redirect vulnerability in Gogs before 0.12 allows remote attackers to redirect users to arbitrary websites and conduct phishing attacks via an initial /\ substring in the user/login redirect_to parameter, related to the function isValidRedirect in routes/user/auth.go. | {'CVE-2018-15178'} | 2021-05-20T20:55:39Z | 2021-06-29T18:32:39Z | MODERATE | null | {'CWE-601'} | {'https://github.com/gogs/gogs/pull/5365', 'https://github.com/gogs/gogs/commit/1f247cf8139cb483276cd8dd06385a800ce9d4b2', 'https://github.com/gogs/gogs/issues/5364', 'https://nvd.nist.gov/vuln/detail/CVE-2018-15178'} | null | {'https://github.com/gogs/gogs/commit/1f247cf8139cb483276cd8dd06385a800ce9d4b2'} | {'https://github.com/gogs/gogs/commit/1f247cf8139cb483276cd8dd06385a800ce9d4b2'} |
Go | GHSA-p2j5-3f4c-224r | Improper Input Validation in HashiCorp Consul | HashiCorp Consul and Consul Enterprise did not appropriately enforce scope for local tokens issued by a primary data center, where replication to a secondary data center was not enabled. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4. | {'CVE-2020-13170'} | 2021-05-12T22:01:59Z | 2021-05-18T18:21:21Z | MODERATE | null | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-13170', 'https://github.com/hashicorp/consul/blob/v1.7.4/CHANGELOG.md', 'https://github.com/hashicorp/consul/pull/8068', 'https://github.com/hashicorp/consul/commit/242994a016a181d6c62a5bb83189716ad13d4216', 'https://github.com/hashicorp/consul/blob/v1.6.6/CHANGELOG.md'} | null | {'https://github.com/hashicorp/consul/commit/242994a016a181d6c62a5bb83189716ad13d4216'} | {'https://github.com/hashicorp/consul/commit/242994a016a181d6c62a5bb83189716ad13d4216'} |
Go | GHSA-9r5x-fjv3-q6h4 | Incorrect Access Control in github.com/nats-io/jwt and github.com/nats-io/nats-server/v2 | NATS Server 2.x before 2.2.0 and JWT library before 2.0.1 have Incorrect Access Control because Import Token bindings are mishandled. | {'CVE-2021-3127'} | 2021-05-12T20:34:10Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-863', 'CWE-284'} | {'https://advisories.nats.io/CVE/CVE-2021-3127.txt', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3127', 'https://github.com/nats-io/jwt/pull/149/commits/a826c77dc9d2671c961b75ceefdb439c41029866', 'https://github.com/nats-io/nats-server/commit/423b79440c80c863de9f4e20548504e6c5d5e403'} | null | {'https://github.com/nats-io/nats-server/commit/423b79440c80c863de9f4e20548504e6c5d5e403', 'https://github.com/nats-io/jwt/pull/149/commits/a826c77dc9d2671c961b75ceefdb439c41029866'} | {'https://github.com/nats-io/nats-server/commit/423b79440c80c863de9f4e20548504e6c5d5e403', 'https://github.com/nats-io/jwt/pull/149/commits/a826c77dc9d2671c961b75ceefdb439c41029866'} |
Go | GO-2021-0051 | null | Due to improper santization of user input on Windows, the static file handler
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/labstack/echo/pull/1718', 'https://github.com/labstack/echo/commit/4422e3b66b9fd498ed1ae1d0242d660d0ed3faaa'} | null | {'https://github.com/labstack/echo/commit/4422e3b66b9fd498ed1ae1d0242d660d0ed3faaa'} | {'https://github.com/labstack/echo/commit/4422e3b66b9fd498ed1ae1d0242d660d0ed3faaa'} |
Go | GHSA-65f3-3278-7m65 | Improper Authorization in Gogs | ### Impact
Expired PAM accounts and accounts with expired passwords are continued to be seen as valid. Installations use PAM as authentication sources are affected.
### Patches
Expired PAM accounts and accounts with expired passwords are no longer being seen as valid. Users should upgrade to 0.12.5 or the latest 0.13.0+dev.
### Workarounds
In addition to marking PAM accounts as expired, also disable/lock them. Running `usermod -L <username>` will add an exclamation mark to the password hash and would result in wrong passwords responses when trying to login.
### References
https://huntr.dev/bounties/ea82cfc9-b55c-41fe-ae58-0d0e0bd7ab62/
### For more information
If you have any questions or comments about this advisory, please post on https://github.com/gogs/gogs/issues/6810.
| {'CVE-2022-0871'} | 2022-03-14T22:58:34Z | 2022-03-12T00:00:34Z | HIGH | null | {'CWE-863', 'CWE-285'} | {'https://huntr.dev/bounties/ea82cfc9-b55c-41fe-ae58-0d0e0bd7ab62', 'https://github.com/gogs/gogs', 'https://github.com/gogs/gogs/commit/64102be2c90e1b47dbdd379873ba76c80d4b0e78', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0871'} | null | {'https://github.com/gogs/gogs/commit/64102be2c90e1b47dbdd379873ba76c80d4b0e78'} | {'https://github.com/gogs/gogs/commit/64102be2c90e1b47dbdd379873ba76c80d4b0e78'} |
Go | GHSA-qhm4-jxv7-j9pq | Allocation of Resources Without Limits or Throttling and Uncontrolled Memory Allocation in Kubernetes | The Kubelet component in versions 1.15.0-1.15.9, 1.16.0-1.16.6, and 1.17.0-1.17.2 has been found to be vulnerable to a denial of service attack via the kubelet API, including the unauthenticated HTTP read-only API typically served on port 10255, and the authenticated HTTPS API typically served on port 10250. | {'CVE-2020-8551'} | 2021-05-06T21:53:58Z | 2022-02-15T01:57:18Z | LOW | null | {'CWE-789'} | {'https://security.netapp.com/advisory/ntap-20200413-0003/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3SOCLOPTSYABTE4CLTSPDIFE6ZZZR4LX/', 'https://github.com/kubernetes/kubernetes/pull/87913', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8551', 'https://github.com/kubernetes/kubernetes/commit/9802bfcec0580169cffce2a3d468689a407fa7dc', 'https://github.com/kubernetes/kubernetes/issues/89377', 'https://groups.google.com/forum/#!topic/kubernetes-security-announce/2UOlsba2g0s'} | null | {'https://github.com/kubernetes/kubernetes/commit/9802bfcec0580169cffce2a3d468689a407fa7dc'} | {'https://github.com/kubernetes/kubernetes/commit/9802bfcec0580169cffce2a3d468689a407fa7dc'} |
Go | GHSA-82hx-w2r5-c2wq | Allocation of Resources Without Limits or Throttling and Uncontrolled Memory Allocation in Kubernetes | The Kubernetes API server component in versions prior to 1.15.9, 1.16.0-1.16.6, and 1.17.0-1.17.2 has been found to be vulnerable to a denial of service attack via successful API requests. | {'CVE-2020-8552'} | 2021-05-06T21:48:16Z | 2022-02-15T01:57:18Z | MODERATE | null | {'CWE-789', 'CWE-400'} | {'https://security.netapp.com/advisory/ntap-20200413-0003/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3SOCLOPTSYABTE4CLTSPDIFE6ZZZR4LX/', 'https://github.com/kubernetes/kubernetes/commit/5978856c4c7f10737a11c9540fe60b8475beecbb', 'https://github.com/kubernetes/kubernetes/issues/89378', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8552', 'https://github.com/kubernetes/kubernetes/pull/87669', 'https://groups.google.com/forum/#!topic/kubernetes-security-announce/2UOlsba2g0s'} | null | {'https://github.com/kubernetes/kubernetes/commit/5978856c4c7f10737a11c9540fe60b8475beecbb'} | {'https://github.com/kubernetes/kubernetes/commit/5978856c4c7f10737a11c9540fe60b8475beecbb'} |
Go | GHSA-fqh4-rh59-xhvf | Denial of service | The package `github.com/pires/go-proxyproto` before 0.5.0 are vulnerable to Denial of Service (DoS) via the parseVersion1() function. The reader in this package is a default bufio.Reader wrapping a net.Conn. It will read from the connection until it finds a newline. Since no limits are implemented in the code, a deliberately malformed V1 header could be used to exhaust memory in a server process using this code - and create a DoS. This can be exploited by sending a stream starting with PROXY and continuing to send data (which does not contain a newline) until the target stops acknowledging. The risk here is small, because only trusted sources should be allowed to send proxy protocol headers. | {'CVE-2021-23351'} | 2021-05-18T21:03:39Z | 2021-05-18T21:07:43Z | MODERATE | null | {'CWE-400'} | {'https://github.com/pires/go-proxyproto/commit/7f48261db810703d173f27f3309a808cc2b49b8b', 'https://github.com/pires/go-proxyproto/pull/71', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C36IBVOZXRTWM7MGTRUTOM56P5RR74VU/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4BNVGJMVI3ZTZ675EFPUHPGXCKCGSX46/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23351', 'https://github.com/pires/go-proxyproto/issues/69', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMPIRESGOPROXYPROTO-1081577'} | null | {'https://github.com/pires/go-proxyproto/commit/7f48261db810703d173f27f3309a808cc2b49b8b'} | {'https://github.com/pires/go-proxyproto/commit/7f48261db810703d173f27f3309a808cc2b49b8b'} |
Go | GO-2021-0092 | null | Uniqueness of JWT IDs (jti) are not checked, allowing the JWT to be
replayed.
| {'CVE-2020-15222'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9', 'https://github.com/ory/fosite/security/advisories/GHSA-v3q9-2p3m-7g43'} | null | {'https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9'} | {'https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9'} |
Go | GHSA-ccxc-vr6p-4858 | Improper Certificate Validation in Cosign | ### Impact
Cosign can be manipulated to claim that an entry for a signature exists in the Rekor transparency log even if it doesn't. This requires the attacker to have pull and push permissions for the signature in OCI. This can happen with both standard signing with a keypair and "keyless signing" with Fulcio.
#### Signing with a keypair
<details>
To reproduce this vulnerability, create a keypair and sign an image. Don't store the signature in Rekor:
```
$ cosign generate-key-pair
$ cosign sign --key cosign.key IMAGE
```
If an attacker has access to the signature in OCI, they can manipulate cosign into believing the entry was stored in Rekor even though it wasn't. To accomplish this, the attacker needs to:
1. Pull the signature image
2. Annotate the signature image with any valid Rekor bundle under the `dev.sigstore.cosign/bundle` annotation
3. Push the signature image back to OCI
Verification then prints out the following:
```
$ cosign verify [--key] [IMAGE]
Verification for [IMAGE] --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The signatures were verified against the specified public key
- Any certificates were verified against the Fulcio roots.
[…]
```
The claim that `Existence of the claims in the transparency log was verified offline` is inaccurate since an entry for this image doesn't exist in the log.
The claim that `Any certificates were verified against the Fulcio roots.` is technically correct but since there were no certificates that should be explicitly called out.
</details>
#### "Keyless signing" with an OIDC flow
<details>
To reproduce this vulnerability, sign the image with a Fulcio identity. Don't store the signature in Rekor:
```
$ COSIGN_EXPERIMENTAL=1 cosign sign IMAGE
[...]
IMAGE appears to be a private repository, please confirm uploading to the transparency log at "https://rekor.sigstore.dev" [Y/N]: n
```
Then, create a keypair and sign the image again. Store an entry for the signature in Rekor:
```
$ cosign generate-key-pair
$ COSIGN_EXPERIMENTAL=1 cosign sign --key cosign.key IMAGE
Enter password for private key: IMAGE appears to be a private repository, please confirm uploading to the transparency log at "https://rekor.sigstore.dev" [Y/N]: y
```
If an attacker has access to the signature in OCI, they can manipulate cosign into believing the entry was stored in Rekor even though it wasn't. To accomplish this, the attacker needs to:
1. Pull the signature image
2. Copy the rekor bundle from the second signature into the first signature under the `dev.sigstore.cosign/bundle` annotation
3. Push the signature image back to OCI
_Note: For this to work, both signatures must occur during the valid lifespan of the certificate (~20 minutes)._
Verification then prints out the following:
```
$ cosign verify [--key] [IMAGE]
Verification for [IMAGE] --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The signatures were verified against the specified public key
- Any certificates were verified against the Fulcio roots.
[…]
```
The claim that `Existence of the claims in the transparency log was verified offline` is inaccurate since an entry for this image doesn't exist in the log.
The claim that `Any certificates were verified against the Fulcio roots.` is technically correct but since there were no certificates that should be explicitly called out.
</details>
### Patches
The vulnerability has been patched in v1.5.2 of cosign.
The `signature` in the `signedEntryTimestamp` provided by Rekor is now compared to the `signature` that is being verified. If these don't match, then an error is returned. If a valid bundle is copied to a different signature, verification should fail.
Cosign output now only informs the user that certificates were verified if a certificate was in fact verified.
### Workarounds
The only workaround is upgrading.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [cosign](https://github.com/sigstore/cosign)
* Send us a message on [Slack](https://sigstore.slack.com/). Invite link [here](https://join.slack.com/t/sigstore/shared_invite/zt-mhs55zh0-XmY3bcfWn4XEyMqUUutbUQ).
### Thank you
Thank you to @mtrmac for finding and reporting this vulnerability.
Thank you to everyone who worked on fixing this:
* @nsmith5
* @znewman01
* @dlorenc
* @mattmoor
* @priyawadhwa
| {'CVE-2022-23649'} | 2022-03-08T18:26:05Z | 2022-02-22T19:34:09Z | LOW | null | {'CWE-295'} | {'https://github.com/sigstore/cosign/security/advisories/GHSA-ccxc-vr6p-4858', 'https://github.com/sigstore/cosign/commit/96d410a6580e4e81d24d112a0855c70ca3fb5b49', 'https://github.com/sigstore/cosign/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23649', 'https://github.com/sigstore/cosign/releases/tag/v1.5.2'} | null | {'https://github.com/sigstore/cosign/commit/96d410a6580e4e81d24d112a0855c70ca3fb5b49'} | {'https://github.com/sigstore/cosign/commit/96d410a6580e4e81d24d112a0855c70ca3fb5b49'} |
Go | GO-2020-0036 | null | Due to unbounded aliasing, a crafted YAML file can cause consumption
of significant system resources. If parsing user supplied input, this
may be used as a denial of service vector.
| {'CVE-2019-11254'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18496', 'https://github.com/go-yaml/yaml/commit/53403b58ad1b561927d19068c655246f2db79d48', 'https://github.com/go-yaml/yaml/pull/555'} | null | {'https://github.com/go-yaml/yaml/commit/53403b58ad1b561927d19068c655246f2db79d48'} | {'https://github.com/go-yaml/yaml/commit/53403b58ad1b561927d19068c655246f2db79d48'} |
Go | GHSA-jr9c-h74f-2v28 | Improper Authorization in Gitea | Gitea 1.16.3 and prior is vulnerable to improper authorization. A patch is available and is anticipated to be part of the 1.16.4 release. | {'CVE-2022-0905'} | 2022-03-28T22:24:29Z | 2022-03-11T00:02:35Z | MODERATE | null | {'CWE-863', 'CWE-285'} | {'https://github.com/go-gitea/gitea/commit/1314f38b59748397b3429fb9bc9f9d6bac85d2f2', 'https://github.com/go-gitea/gitea', 'https://huntr.dev/bounties/8d221f92-b2b1-4878-bc31-66ff272e5ceb', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0905'} | null | {'https://github.com/go-gitea/gitea/commit/1314f38b59748397b3429fb9bc9f9d6bac85d2f2'} | {'https://github.com/go-gitea/gitea/commit/1314f38b59748397b3429fb9bc9f9d6bac85d2f2'} |
Go | GHSA-xcqr-9h24-vrgw | Improper Restriction of Excessive Authentication Attempts in Argo API | As of v1.5.0, the Argo API does not implement anti-automation measures such as rate limiting, account lockouts, or other anti-bruteforce measures. Attackers can submit an unlimited number of authentication attempts without consequence. | {'CVE-2020-8827'} | 2021-07-26T21:13:31Z | 2021-07-26T21:19:37Z | HIGH | null | {'CWE-307'} | {'https://argoproj.github.io/argo-cd/security_considerations/', 'https://www.soluble.ai/blog/argo-cves-2020', 'https://github.com/argoproj/argo-cd/pull/3369', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8827', 'https://github.com/argoproj/argo-cd/pull/3404', 'https://github.com/argoproj/argo/releases', 'https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1', 'https://argoproj.github.io/argo-cd/operator-manual/user-management/#disable-admin-user'} | null | {'https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1'} | {'https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1'} |
Go | GHSA-wjm3-fq3r-5x46 | Denial of service | GJSON <1.6.5 allows attackers to cause a denial of service (remote) via crafted JSON. | {'CVE-2020-36066'} | 2021-05-18T21:00:38Z | 2021-05-18T21:07:54Z | MODERATE | null | {'CWE-400'} | {'https://github.com/tidwall/match/commit/c2f534168b739a7ec1821a33839fb2f029f26bbc', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36066', 'https://github.com/tidwall/gjson/issues/195#issuecomment-755303148', 'https://github.com/tidwall/gjson/issues/195'} | null | {'https://github.com/tidwall/match/commit/c2f534168b739a7ec1821a33839fb2f029f26bbc'} | {'https://github.com/tidwall/match/commit/c2f534168b739a7ec1821a33839fb2f029f26bbc'} |
Go | GHSA-8v99-48m9-c8pm | Incorrect Authorization in imgcrypt | Imgcrypt implements a function `CheckAuthorization()` that is supposed to check whether a user is authorized to access an encrypted image given the keys that the user has provided on the command line that would enable decryption of the image. The check is to prevent that a user can start a container from an image that has previously been decrypted by another user on the same system and therefore a decrypted version of the image layers may be already available in the cache locally.
The failure occurs when an image with a ManifestList is used and the architecture of the local host is not the first one in the ManifestList. In the version prior to the fix, only the first architecture in the list was tested, which may not have its layers available locally (were not pulled) since it cannot be run on the host architecture. Therefore, the verdict on unavailable layers was that the image could be run anticipating that image run failure would occur later due to the layers not being available. However, this verdict to allow the image to run lead to other architectures in the ManifestList be able to run an image without providing keys if that image had previously been decrypted. The fixed version now skips over irrelevant architectures and tests the Manifest of the local architecture, if available.
Known projects that use the `CheckAuthorization()` of imgcrypt is for example the ctr-enc client tool provided by imgcrypt. In this implementation, the call to `CheckAuthorization()` is used on the client side and could therefore also be easily circumvented by a modified client tool not calling this function.
In relation to the vulnerability in ctr-enc, affected environments would have to allow different users to invoke ctr-enc indirectly using some sort of management stack that gives user indirect access to ctr-enc.
The patch has been applied to imgcrypt v1.1.4. Workarounds may include usage of different namespaces for each remote user. | {'CVE-2022-24778'} | 2022-04-13T03:57:32Z | 2022-03-28T19:33:44Z | HIGH | null | {'CWE-863'} | {'https://github.com/containerd/imgcrypt/issues/69', 'https://github.com/containerd/imgcrypt/security/advisories/GHSA-8v99-48m9-c8pm', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TAHAAOOA3KZJC2I5WHCR3XVBJBNWTWUE/', 'https://github.com/containerd/imgcrypt/releases/tag/v1.1.4', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZFTJR5CR5EOYDVOSBZEMLBHLJRTPJPUA/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24778', 'https://github.com/containerd/imgcrypt/commit/6fdd9818a4d8142107b7ecd767d839c9707700d9', 'https://github.com/containerd/imgcrypt'} | null | {'https://github.com/containerd/imgcrypt/commit/6fdd9818a4d8142107b7ecd767d839c9707700d9'} | {'https://github.com/containerd/imgcrypt/commit/6fdd9818a4d8142107b7ecd767d839c9707700d9'} |
Go | GHSA-qqc5-rgcc-cjqh | Information Disclosure in go.elastic.co/apm | The Elastic APM agent for Go versions before 1.11.0 can leak sensitive HTTP header information when logging the details during an application panic. Normally, the APM agent will sanitize sensitive HTTP header details before sending the information to the APM server. During an application panic it is possible the headers will not be sanitized before being sent. | {'CVE-2021-22133'} | 2021-05-07T22:01:55Z | 2021-05-18T18:34:18Z | LOW | null | {'CWE-532'} | {'https://github.com/elastic/apm-agent-go/commit/c5c7e21aa26a6def7790f74fbceed792ad47ef35', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22133', 'https://github.com/elastic/apm-agent-go/compare/v1.10.0...v1.11.0', 'https://discuss.elastic.co/t/elastic-apm-agent-for-go-1-11-0-security-update/263252'} | null | {'https://github.com/elastic/apm-agent-go/commit/c5c7e21aa26a6def7790f74fbceed792ad47ef35'} | {'https://github.com/elastic/apm-agent-go/commit/c5c7e21aa26a6def7790f74fbceed792ad47ef35'} |
Go | GO-2021-0084 | null | Session data is stored using permissive permissions, allowing local users
with filesystem access to read arbitary data.
| {'CVE-2019-16354'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/beego/beego/commit/bac2b31afecc65d9a89f9e473b8006c5edc0c8d1', 'https://github.com/beego/beego/issues/3763', 'https://github.com/beego/beego/pull/3975'} | null | {'https://github.com/beego/beego/commit/bac2b31afecc65d9a89f9e473b8006c5edc0c8d1'} | {'https://github.com/beego/beego/commit/bac2b31afecc65d9a89f9e473b8006c5edc0c8d1'} |
Go | GHSA-f9fq-vjvh-779p | Improper Input Validation in vault-ssh-helper | HashiCorp vault-ssh-helper up to and including version 0.1.6 incorrectly accepted Vault-issued SSH OTPs for the subnet in which a host's network interface was located, rather than the specific IP address assigned to that interface. Fixed in 0.2.0. | {'CVE-2020-24359'} | 2021-05-12T20:21:27Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-20'} | {'https://github.com/hashicorp/vault-ssh-helper/commit/83effd08cbcbe4b993d776bd9b39465cd9e4603f', 'https://nvd.nist.gov/vuln/detail/CVE-2020-24359', 'https://github.com/hashicorp/vault-ssh-helper/blob/master/CHANGELOG.md#020-august-19-2020', 'https://github.com/hashicorp/vault-ssh-helper/releases'} | null | {'https://github.com/hashicorp/vault-ssh-helper/commit/83effd08cbcbe4b993d776bd9b39465cd9e4603f'} | {'https://github.com/hashicorp/vault-ssh-helper/commit/83effd08cbcbe4b993d776bd9b39465cd9e4603f'} |
Go | GHSA-h2fg-54x9-5qhq | Nil dereference in NATS JWT, DoS of nats-server | ## Problem Description
The NATS account system has an Operator trusted by the servers, which signs Accounts, and each Account can then create and sign Users within their account. The Operator should be able to safely issue Accounts to other entities which it does not fully trust.
A malicious Account could create and sign a User JWT with a state not created by the normal tooling, such that decoding by the NATS JWT library (written in Go) would attempt a nil dereference, aborting execution.
The NATS Server is known to be impacted by this.
## Affected versions
#### JWT library
* all versions prior to 1.1.0
#### NATS Server
* Version 2 prior to 2.1.9
## Impact
#### JWT library
* Programs would nil dereference and panic, aborting execution by default.
#### NATS server
* Denial of Service caused by process termination
## Workaround
If your NATS servers do not trust any accounts which are managed by untrusted entities, then malformed User credentials are unlikely to be encountered.
## Solution
Upgrade the JWT dependency in any application using it.
Upgrade the NATS server if using NATS Accounts. | {'CVE-2020-26521'} | 2022-02-11T23:43:13Z | 2022-02-11T23:43:13Z | LOW | null | {'CWE-476'} | {'https://github.com/nats-io/jwt/security/advisories/GHSA-h2fg-54x9-5qhq', 'http://www.openwall.com/lists/oss-security/2020/11/02/2', 'https://github.com/nats-io/nats-server/commits/master', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26521', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VT67XCLIIBYRT762SVFBYFFTQFVSM3SI/', 'https://github.com/nats-io/nats-server/commit/9ff8bcde2e46009e98bd9e88f598af355f62c168', 'https://advisories.nats.io/CVE/CVE-2020-26521.txt'} | null | {'https://github.com/nats-io/nats-server/commit/9ff8bcde2e46009e98bd9e88f598af355f62c168'} | {'https://github.com/nats-io/nats-server/commit/9ff8bcde2e46009e98bd9e88f598af355f62c168'} |
Go | GO-2020-0020 | null | Usage of the [`CORS`] handler may apply improper CORS headers, allowing
the requester to explicitly control the value of the Access-Control-Allow-Origin
header, which bypasses the expected behavior of the Same Origin Policy.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/gorilla/handlers/pull/116', 'https://github.com/gorilla/handlers/commit/90663712d74cb411cbef281bc1e08c19d1a76145'} | null | {'https://github.com/gorilla/handlers/commit/90663712d74cb411cbef281bc1e08c19d1a76145'} | {'https://github.com/gorilla/handlers/commit/90663712d74cb411cbef281bc1e08c19d1a76145'} |
Go | GHSA-6jqj-f58p-mrw3 | Denial of Service in TenderMint | ### Description
**Denial of Service**
Tendermint 0.33.0 and above allow block proposers to include signatures for the wrong block. This may happen naturally if you start a network, have it run for some time and restart it without changing the chainID. (It is a [misconfiguration](https://docs.tendermint.com/master/tendermint-core/using-tendermint.html) to reuse chainIDs.) Correct block proposers will accidentally include signatures for the wrong block if they see these signatures, and then commits won't validate, making all proposed blocks invalid. A malicious validator (even with a minimal amount of stake) can use this vulnerability to completely halt the network.
Tendermint 0.33.6 checks all the signatures are for the block with +2/3 majority before creating a commit.
**False Witness**
Tendermint 0.33.1 and above are no longer fully verifying commit signatures during block execution - they stop after +2/3. This means proposers can propose blocks that contain valid +2/3 signatures and then the rest of the signatures can be whatever they want. They can claim that all the other validators signed just by including a CommitSig with arbitrary signature data. While this doesn't seem to impact safety of Tendermint per se, it means that Commits may contain a lot of invalid data **.
_** This was already true of blocks, since they could include invalid txs filled with garbage, but in that case the application knew that they are invalid and could punish the proposer. But since applications didn't--and don't-- verify commit signatures directly (they trust Tendermint to do that), they won't be able to detect it._
This can impact incentivization logic in the application that depends on the LastCommitInfo sent in BeginBlock, which includes which validators signed. For instance, Gaia incentivizes proposers with a bonus for including more than +2/3 of the signatures. But a proposer can now claim that bonus just by including arbitrary data for the final -1/3 of validators without actually waiting for their signatures. There may be other tricks that can be played because of this.
Tendermint 0.33.6 verifies all the signatures during block execution ***.
_*** Please note that the light client does not check nil votes and exits as soon as 2/3+ of the signatures are checked._
### Impact
- All nodes
- The network stops due to having a commit with a wrong signature.
### Patches
- v0.33.6
### Workarounds
No workarounds.
### References
- https://github.com/tendermint/tendermint/issues/4926
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint)
* Email us at [security@tendermint.com](mailto:security@tendermint.com)
More information can be found [here](https://tendermint.com/security/). | {'CVE-2020-15091'} | 2021-05-24T20:49:56Z | 2021-12-20T18:17:33Z | MODERATE | null | {'CWE-347'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15091', 'https://github.com/tendermint/tendermint/security/advisories/GHSA-6jqj-f58p-mrw3', 'https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340', 'https://github.com/tendermint/tendermint/issues/4926'} | null | {'https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340'} | {'https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340'} |
Go | GO-2020-0016 | null | An attacker can construct a series of bytes such that calling
[`Reader.Read`] on the bytes could cause an infinite loop. If
parsing user supplied input, this may be used as a denial of
service vector.
| {'CVE-2021-29482'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/ulikunitz/xz/security/advisories/GHSA-25xm-hr59-7c27', 'https://github.com/ulikunitz/xz/issues/35', 'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b'} | null | {'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b'} | {'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b'} |
Go | GHSA-5m6c-jp6f-2vcv | Open Redirect in OAuth2 Proxy | ### Impact
As users can provide a redirect address for the proxy to send the authenticated user to at the end of the authentication flow. This is expected to be the original URL that the user was trying to access.
This redirect URL is checked within the proxy and validated before redirecting the user to prevent malicious actors providing redirects to potentially harmful sites. | {'CVE-2020-4037'} | 2021-05-24T20:58:18Z | 2021-12-20T17:58:59Z | MODERATE | null | {'CWE-601'} | {'https://github.com/oauth2-proxy/oauth2-proxy/releases/tag/v6.0.0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-4037', 'https://github.com/oauth2-proxy/oauth2-proxy/commit/ee5662e0f5001d76ec76562bb605abbd07c266a2', 'https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-5m6c-jp6f-2vcv'} | null | {'https://github.com/oauth2-proxy/oauth2-proxy/commit/ee5662e0f5001d76ec76562bb605abbd07c266a2'} | {'https://github.com/oauth2-proxy/oauth2-proxy/commit/ee5662e0f5001d76ec76562bb605abbd07c266a2'} |
Go | GO-2020-0041 | null | Due to improper path santization, archives containing relative file
paths can cause files to be written (or overwritten) outside of the
target directory.
| {'CVE-2020-7668'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://snyk.io/research/zip-slip-vulnerability', 'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11'} | null | {'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11'} | {'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11'} |
Go | GHSA-jm34-xm8m-w958 | Open Redirect in oauth2_proxy | The Bitly oauth2_proxy in version 2.1 and earlier was affected by an open redirect vulnerability during the start and termination of the 2-legged OAuth flow. This issue was caused by improper input validation and a violation of RFC-6819 | {'CVE-2017-1000070'} | 2021-05-19T22:31:56Z | 2021-12-20T18:04:40Z | MODERATE | null | {'CWE-601'} | {'https://github.com/bitly/oauth2_proxy/pull/359', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000070', 'https://github.com/bitly/oauth2_proxy/issues/228', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000070', 'https://tools.ietf.org/html/rfc6819#section-5.2.3.5', 'https://github.com/bitly/oauth2_proxy/commit/289a6ccf463a425c7606178c510fc5eeb9c8b050'} | null | {'https://github.com/bitly/oauth2_proxy/commit/289a6ccf463a425c7606178c510fc5eeb9c8b050'} | {'https://github.com/bitly/oauth2_proxy/commit/289a6ccf463a425c7606178c510fc5eeb9c8b050'} |
Go | GO-2021-0071 | null | A race between chown and chmod operations during a container filesystem shift
may allow a user who can modify the filesystem to chmod an arbitary path of
their choice, rather than the expected path.
| {'CVE-2015-1340'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1502270', 'https://github.com/lxc/lxd/commit/19c6961cc1012c8a529f20807328a9357f5034f4', 'https://github.com/lxc/lxd/pull/1189'} | null | {'https://github.com/lxc/lxd/commit/19c6961cc1012c8a529f20807328a9357f5034f4'} | {'https://github.com/lxc/lxd/commit/19c6961cc1012c8a529f20807328a9357f5034f4'} |
Go | GHSA-4mf2-f3wh-gvf2 | Subdomain checking of whitelisted domains could allow unintended redirects in oauth2-proxy | ### Impact
_What kind of vulnerability is it? Who is impacted?_
For users that use the whitelist domain feature, a domain that ended in a similar way to the intended domain could have been allowed as a redirect.
For example, if a whitelist domain was configured for `.example.com`, the intention is that subdomains of `example.com` are allowed.
Instead, `example.com` and `badexample.com` could also match.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
This is fixed in version 7.0.0 onwards.
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Disable the whitelist domain feature and run separate OAuth2 Proxy instances for each subdomain.
# Original Issue Posted by @semoac:
Whitelist Domain feature is not working as expected because is not matching a dot to ensure the redirect is a subdomain.
## Expected Behavior
If whitelist domain is set to `.example.com` , then `hack.alienexample.com` should be rejected as a valid redirect.
## Current Behavior
The code is removing the `dot` from `.example.com` and only checking if the redirect string end with `example.com`
## Possible Solution
Here
https://github.com/oauth2-proxy/oauth2-proxy/blob/c377466411f2aee180a732187edb638f2f7e57fb/oauthproxy.go#L661
Include the dot when checking the string:
```
strings.HasSuffix(redirectHostname, "." + domainHostname)
```
## Steps to Reproduce (for bugs)
```
package main
import (
"fmt"
"strings"
)
func validOptionalPort(port string) bool {
if port == "" || port == ":*" {
return true
}
if port[0] != ':' {
return false
}
for _, b := range port[1:] {
if b < '0' || b > '9' {
return false
}
}
return true
}
func splitHostPort(hostport string) (host, port string) {
host = hostport
colon := strings.LastIndexByte(host, ':')
if colon != -1 && validOptionalPort(host[colon:]) {
host, port = host[:colon], host[colon+1:]
}
if strings.HasPrefix(host, "[") && strings.HasSuffix(host, "]") {
host = host[1 : len(host)-1]
}
return
}
func main() {
domain := ".example.com"
domainHostname, _ := splitHostPort(strings.TrimLeft(domain, "."))
redirectHostname := "https://hack.alienexample.com"
if (strings.HasPrefix(domain, ".") && strings.HasSuffix(redirectHostname, domainHostname)) { fmt.Println("This should not have happen.")}
}
```
Users of `github.com/oauth2-proxy/oauth2-proxy` are advised to update to `github.com/oauth2-proxy/oauth2-proxy/v7` | {'CVE-2021-21291'} | 2021-05-21T21:37:23Z | 2021-05-25T18:42:20Z | LOW | null | {'CWE-601'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21291', 'https://github.com/oauth2-proxy/oauth2-proxy/commit/780ae4f3c99b579cb2ea9845121caebb6192f725', 'https://github.com/oauth2-proxy/oauth2-proxy/releases/tag/v7.0.0', 'https://pkg.go.dev/github.com/oauth2-proxy/oauth2-proxy/v7', 'https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-4mf2-f3wh-gvf2'} | null | {'https://github.com/oauth2-proxy/oauth2-proxy/commit/780ae4f3c99b579cb2ea9845121caebb6192f725'} | {'https://github.com/oauth2-proxy/oauth2-proxy/commit/780ae4f3c99b579cb2ea9845121caebb6192f725'} |
Go | GHSA-fx5p-f64h-93xc | Opened exploitable ports in default docker-compose.yaml in go-ipfs | ### Impact
Allows admin API access to the IPFS node.
### Who ?
This affects people running the [docker-compose.yaml](https://github.com/ipfs/go-ipfs/blob/master/docker-compose.yaml) service in an environment where the docker host is directly attached to a public or untrusted IP. In the vulnerable version, the private API endpoint is publicly forwarded by exposing it as `0.0.0.0:5001` on the host machine.
If the host machine is hidden behind a firewall or NAT (and the LAN is trusted for NAT), this is not an immediate issue because of the protection from the firewall or NAT. That said, we still recommend users update to follow security best practices of not putting unnecessary dependency on a working firewall.
### Patches
This issue is in [docker-compose.yaml](https://github.com/ipfs/go-ipfs/blob/master/docker-compose.yaml). Users need to replace their current `docker-compose.yaml` file with a version `0.12.1` or later.
There is no need to update any of the binaries. Users running previous versions like `0.12.0` or earlier can download the `0.12.1` `docker-compose.yaml` file. You can replace a vulnerable `docker-compose.yaml` file with a the new one with:
```
curl https://raw.githubusercontent.com/ipfs/go-ipfs/v0.12.1/docker-compose.yaml > docker-compose.yaml
```
### How to test if you are vulnerable
#### Binding check on the host
On the host machine, while IPFS is running, run as root:
```bash
netstat -lnp | grep ":5001"
```
The output will be a list of listeners bound to `:5001`.
You then need to check that those listeners are private and preferably even localhost IPs.
⚠️ If this listener is on `0.0.0.0` or a public IP you are very likely vulnerable.
#### Remote hailing
While IPFS is running, you can try to contact the API from a remote machine. (Replace `1.2.3.4` with your node public IP. Or if you want to test in an untrusted NAT, then substitute the LAN IP instead.)
```bash
curl -X POST http://1.2.3.4:5001/api/v0/version
```
⚠️ If you see any json outputted (e.g., `{"Commit": "<string>","Golang": "<string>","Repo": "<string>","System": "<string>","Version": "<string>"}`), then you are vulnerable.
If it **fails**, then you are safe.
### For more information
If you have any questions or comments about this advisory:
* Please first read https://docs.ipfs.io/reference/http/api/ about best practices
* Ask in [IPFS Discord #ipfs-chatter](https://discord.gg/ipfs)
* Open an issue in [go-ipfs](https://github.com/ipfs/go-ipfs)
| null | 2022-04-04T21:23:55Z | 2022-04-04T21:23:55Z | MODERATE | null | null | {'https://github.com/ipfs/go-ipfs/commit/816a128aaf963d72c4930852ce32b9a4e31924a1', 'https://github.com/ipfs/go-ipfs/releases/tag/v0.12.1', 'https://github.com/ipfs/go-ipfs/pull/8773', 'https://github.com/ipfs/go-ipfs/security/advisories/GHSA-fx5p-f64h-93xc', 'https://github.com/ipfs/go-ipfs'} | null | {'https://github.com/ipfs/go-ipfs/commit/816a128aaf963d72c4930852ce32b9a4e31924a1'} | {'https://github.com/ipfs/go-ipfs/commit/816a128aaf963d72c4930852ce32b9a4e31924a1'} |
Go | GHSA-xcf7-q56x-78gh | Connection descriptor exhaustion in proxyproto | The package `github.com/pires/go-proxyproto` before 0.6.0 are vulnerable to Denial of Service (DoS) via creating connections without the proxy protocol header. | {'CVE-2021-23409'} | 2021-07-26T17:31:53Z | 2021-07-26T21:23:49Z | HIGH | null | {'CWE-400'} | {'https://github.com/pires/go-proxyproto/issues/65', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMPIRESGOPROXYPROTO-1316439', 'https://github.com/pires/go-proxyproto/pull/74/commits/cdc63867da24fc609b727231f682670d0d1cd346', 'https://github.com/pires/go-proxyproto/releases/tag/v0.6.0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23409', 'https://github.com/pires/go-proxyproto/pull/74'} | null | {'https://github.com/pires/go-proxyproto/pull/74/commits/cdc63867da24fc609b727231f682670d0d1cd346'} | {'https://github.com/pires/go-proxyproto/pull/74/commits/cdc63867da24fc609b727231f682670d0d1cd346'} |
Go | GHSA-x5m6-jh4r-34mv | Arbitrary File Overwrite in hub | The am function in lib/hub/commands.rb in hub before 1.12.1 allows local users to overwrite arbitrary files via a symlink attack on a temporary patch file. | {'CVE-2014-0177'} | 2021-05-20T20:32:04Z | 2022-02-15T01:07:53Z | MODERATE | null | {'CWE-377'} | {'https://github.com/github/hub/commit/016ec99d25b1cb83cb4367e541177aa431beb600', 'https://nvd.nist.gov/vuln/detail/CVE-2014-0177', 'https://secunia.com/advisories/58273'} | null | {'https://github.com/github/hub/commit/016ec99d25b1cb83cb4367e541177aa431beb600'} | {'https://github.com/github/hub/commit/016ec99d25b1cb83cb4367e541177aa431beb600'} |
Go | GHSA-7gfg-6934-mqq2 | Improper Authenication in Pion DTLS | handleIncomingPacket in conn.go in Pion DTLS before 1.5.2 lacks a check for application data with epoch 0, which allows remote attackers to inject arbitrary unencrypted data after handshake completion. | {'CVE-2019-20786'} | 2021-05-25T19:54:18Z | 2021-06-29T21:34:57Z | CRITICAL | null | {'CWE-287'} | {'https://www.usenix.org/system/files/sec20fall_fiterau-brostean_prepub.pdf', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20786', 'https://github.com/pion/dtls/compare/v1.5.1...v1.5.2', 'https://github.com/pion/dtls/commit/fd73a5df2ff0e1fb6ae6a51e2777d7a16cc4f4e0', 'https://www.usenix.org/conference/usenixsecurity20/presentation/fiterau-brostean'} | null | {'https://github.com/pion/dtls/commit/fd73a5df2ff0e1fb6ae6a51e2777d7a16cc4f4e0'} | {'https://github.com/pion/dtls/commit/fd73a5df2ff0e1fb6ae6a51e2777d7a16cc4f4e0'} |
Go | GHSA-rrm8-32g4-w8m3 | Cross-site Request Forgery (CSRF) | CSRF in Bitly oauth2_proxy 2.1 during authentication flow | {'CVE-2017-1000069'} | 2021-05-12T18:30:22Z | 2021-12-20T18:04:46Z | HIGH | null | {'CWE-352'} | {'https://github.com/bitly/oauth2_proxy/commit/55085d9697962668fd4e43e8e4644144fe83cd93', 'https://github.com/bitly/oauth2_proxy/pull/360', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000069', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000069'} | null | {'https://github.com/bitly/oauth2_proxy/commit/55085d9697962668fd4e43e8e4644144fe83cd93'} | {'https://github.com/bitly/oauth2_proxy/commit/55085d9697962668fd4e43e8e4644144fe83cd93'} |
Go | GHSA-wmwp-pggc-h4mj | Cross-site Scripting in Documize | domain/section/markdown/markdown.go in Documize before 3.5.1 mishandles untrusted Markdown content. This was addressed by adding the bluemonday HTML sanitizer to defend against XSS. | {'CVE-2019-19619'} | 2021-05-17T21:29:00Z | 2021-05-18T15:30:30Z | MODERATE | null | {'CWE-79'} | {'https://github.com/documize/community/compare/v3.5.0...v3.5.1', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19619', 'https://github.com/documize/community/releases/tag/v3.5.1', 'https://github.com/documize/community/commit/a4384210d4d0d6b18e6fdb7e155de96d4a1cf9f3'} | null | {'https://github.com/documize/community/commit/a4384210d4d0d6b18e6fdb7e155de96d4a1cf9f3'} | {'https://github.com/documize/community/commit/a4384210d4d0d6b18e6fdb7e155de96d4a1cf9f3'} |
Go | GO-2021-0067 | null | Using Reader.Open on an archive containing a file with a path
prefixed by "../" will cause a panic due to a stack overflow.
If parsing user supplied archives, this may be used as a
denial of service vector.
| {'CVE-2021-27919'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/golang/go/issues/44916', 'https://go-review.googlesource.com/c/go/+/300489', 'https://github.com/golang/go/commit/cd3b4ca9f20fd14187ed4cdfdee1a02ea87e5cd8'} | null | {'https://github.com/golang/go/commit/cd3b4ca9f20fd14187ed4cdfdee1a02ea87e5cd8'} | {'https://github.com/golang/go/commit/cd3b4ca9f20fd14187ed4cdfdee1a02ea87e5cd8'} |
Go | GHSA-3fx4-7f69-5mmg | Integer Overflow in go-jose | go-jose before 1.0.5 suffers from a CBC-HMAC integer overflow on 32-bit architectures. An integer overflow could lead to authentication bypass for CBC-HMAC encrypted ciphertexts on 32-bit architectures. | {'CVE-2016-9123'} | 2021-05-20T16:26:07Z | 2021-06-23T17:14:12Z | HIGH | null | {'CWE-190'} | {'https://github.com/square/go-jose/commit/789a4c4bd4c118f7564954f441b29c153ccd6a96', 'https://nvd.nist.gov/vuln/detail/CVE-2016-9123', 'https://www.openwall.com/lists/oss-security/2016/11/03/1', 'https://hackerone.com/reports/165170'} | null | {'https://github.com/square/go-jose/commit/789a4c4bd4c118f7564954f441b29c153ccd6a96'} | {'https://github.com/square/go-jose/commit/789a4c4bd4c118f7564954f441b29c153ccd6a96'} |
Go | GO-2021-0088 | null | Skip ignores unknown fields, rather than failing. A malicious user can craft small
messages with unknown fields which can take significant resources to parse. If a
server accepts messages from an untrusted user, it may be used as a denial of service
vector.
| {'CVE-2019-3564'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://www.facebook.com/security/advisories/cve-2019-3564', 'https://github.com/facebook/fbthrift/commit/c461c1bd1a3e130b181aa9c854da3030cd4b5156'} | null | {'https://github.com/facebook/fbthrift/commit/c461c1bd1a3e130b181aa9c854da3030cd4b5156'} | {'https://github.com/facebook/fbthrift/commit/c461c1bd1a3e130b181aa9c854da3030cd4b5156'} |
Go | GHSA-gv2h-gf8m-r68j | Exposure of server configuration in github.com/go-vela/server | ### Impact
_What kind of vulnerability is it? Who is impacted?_
* The ability to expose configuration set in the [Vela server](https://github.com/go-vela/server) via [pipeline template functionality](https://go-vela.github.io/docs/templates/overview/).
* It impacts all users of Vela.
Sample of template exposing server configuration [using Sprig's `env` function](http://masterminds.github.io/sprig/os.html):
```yaml
metadata:
template: true
steps:
- name: sample
image: alpine:latest
commands:
# OAuth client ID for Vela <-> GitHub communication
- echo {{ env "VELA_SOURCE_CLIENT" }}
# secret used for server <-> worker communication
- echo {{ env "VELA_SECRET" }}
```
### Patches
_Has the problem been patched? What versions should users upgrade to?_
* Upgrade to `0.6.1`
#### Additional Recommended Action(s)
* Rotate all secrets
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
* No
### For more information
If you have any questions or comments about this advisory:
* Email us at [vela@target.com](mailto:vela@target.com) | {'CVE-2020-26294'} | 2022-02-15T00:19:57Z | 2022-02-15T00:19:57Z | HIGH | null | {'CWE-200', 'CWE-78'} | {'https://pkg.go.dev/github.com/go-vela/compiler/compiler', 'https://github.com/go-vela/compiler/commit/f1ace5f8a05c95c4d02264556e38a959ee2d9bda', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26294', 'https://github.com/go-vela/compiler/security/advisories/GHSA-gv2h-gf8m-r68j', 'https://github.com/helm/helm/blob/6297c021cbda1483d8c08a8ec6f4a99e38be7302/pkg/engine/funcs.go#L46-L47'} | null | {'https://github.com/go-vela/compiler/commit/f1ace5f8a05c95c4d02264556e38a959ee2d9bda'} | {'https://github.com/go-vela/compiler/commit/f1ace5f8a05c95c4d02264556e38a959ee2d9bda'} |
Go | GHSA-q6gq-997w-f55g | Infinite loop in xz | Go before 1.13.15 and 14.x before 1.14.7 can have an infinite read loop in ReadUvarint and ReadVarint in encoding/binary via invalid inputs. | {'CVE-2020-16845'} | 2021-06-18T22:05:40Z | 2021-12-16T19:16:40Z | HIGH | null | {'CWE-835'} | {'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00029.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00030.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TACQFZDPA7AUR6TRZBCX2RGRFSDYLI7O/', 'http://lists.opensuse.org/opensuse-security-announce/2020-08/msg00028.html', 'https://security.netapp.com/advisory/ntap-20200924-0002/', 'https://groups.google.com/forum/#!topic/golang-announce/_ulYYcIWg3Q', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://github.com/ulikunitz/xz/issues/35', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6RCFJTMKHY5ICGEM5BUFUEDDGSPJ25XU/', 'https://lists.debian.org/debian-lts-announce/2020/11/msg00038.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WV2VWKFTH4EJGZBZALVUJQJOAQB5MDQ4/', 'https://lists.debian.org/debian-lts-announce/2020/11/msg00037.html', 'https://groups.google.com/forum/#!topic/golang-announce/NyPIaucMgXo', 'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b', 'https://nvd.nist.gov/vuln/detail/CVE-2020-16845', 'http://lists.opensuse.org/opensuse-security-announce/2020-08/msg00021.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KWRBAH4UZJO3RROQ72SYCUPFCJFA22FO/', 'https://www.debian.org/security/2021/dsa-4848'} | null | {'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b'} | {'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b'} |
Go | GHSA-gmq2-39ff-f5qg | A failed upgrade may lead to hung goroutines | ### Impact
Processes using tableflip may encounter hung goroutines in the parent process, after a failed upgrade.
The Go runtime has annoying behaviour around setting and clearing
O_NONBLOCK: exec.Cmd.Start() ends up calling os.File.Fd() for any
file in exec.Cmd.ExtraFiles. os.File.Fd() disables both the use
of the runtime poller for the file and clears O_NONBLOCK from
the underlying open file descriptor.
This can lead to goroutines hanging in a parent process, after at least
one failed upgrade. The bug manifests in goroutines which rely on
either a deadline or interruption via Close() to be unblocked being stuck
in read or accept like syscalls. As far as I can tell we've not experienced
this problem in production, so it's most likely quite rare.
### Patches
The problem has been fixed in v1.2.2.
### Workarounds
None.
### References
* https://github.com/cloudflare/tableflip/commit/cae714b289e199db5da5f08af861ea65be6232c0 | null | 2021-05-21T14:40:36Z | 2021-05-21T16:25:48Z | LOW | null | null | {'https://github.com/cloudflare/tableflip/security/advisories/GHSA-gmq2-39ff-f5qg', 'https://github.com/cloudflare/tableflip/commit/cae714b289e199db5da5f08af861ea65be6232c0'} | null | {'https://github.com/cloudflare/tableflip/commit/cae714b289e199db5da5f08af861ea65be6232c0'} | {'https://github.com/cloudflare/tableflip/commit/cae714b289e199db5da5f08af861ea65be6232c0'} |
Go | GO-2020-0003 | null | If the application accepts
[slice parameters](https://revel.github.io/manual/parameters.html#slices), an
attacker can cause the application to allocate large amounts of memory and
crash by manipulating the request query.
| null | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/revel/revel/commit/d160ecb72207824005b19778594cbdc272e8a605', 'https://github.com/revel/revel/pull/1427', 'https://github.com/revel/revel/issues/1424'} | null | {'https://github.com/revel/revel/commit/d160ecb72207824005b19778594cbdc272e8a605'} | {'https://github.com/revel/revel/commit/d160ecb72207824005b19778594cbdc272e8a605'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.