id
stringlengths 13
16
| published
stringlengths 19
19
| modified
timestamp[ns] | details
stringlengths 30
3.87k
| severity
listlengths 1
1
⌀ | repo_url
stringlengths 23
68
| cwes
sequencelengths 0
1
| commits
sequencelengths 1
4
|
---|---|---|---|---|---|---|---|
CVE-2024-38361 | 2024-06-20T23:15:52 | 2025-01-15T05:14:46.359892 | Spicedb is an Open Source, Google Zanzibar-inspired permissions database to enable fine-grained authorization for customer applications. Use of an exclusion under an arrow that has multiple resources may resolve to `NO_PERMISSION` when permission is expected. If the resource exists under *multiple* folders and the user has access to view more than a single folder, SpiceDB may report the user does not have access due to a failure in the exclusion dispatcher to request that *all* the folders in which the user is a member be returned. Permission is returned as `NO_PERMISSION` when `PERMISSION` is expected on the `CheckPermission` API. This issue has been addressed in version 1.33.1. All users are advised to upgrade. There are no known workarounds for this issue. | null | https://github.com/authzed/spicedb | [] | [
"10616c73e4dfcebb282372ec8d4d878cf220ec94"
] |
CVE-2024-46989 | 2024-09-18T18:15:07 | 2024-10-08T04:23:12.974115 | spicedb is an Open Source, Google Zanzibar-inspired permissions database to enable fine-grained authorization for customer applications. Multiple caveats over the same indirect subject type on the same relation can result in no permission being returned when permission is expected. If the resource has multiple groups, and each group is caveated, it is possible for the returned permission to be "no permission" when permission is expected. Permission is returned as NO_PERMISSION when PERMISSION is expected on the CheckPermission API. This issue has been addressed in release version 1.35.3. Users are advised to upgrade. Users unable to upgrade should not use caveats or avoid the use of caveats on an indirect subject type with multiple entries. | null | https://github.com/authzed/spicedb | [] | [
"10616c73e4dfcebb282372ec8d4d878cf220ec94"
] |
CVE-2024-48909 | 2024-10-14T21:15:12 | 2024-10-17T18:49:51.159801 | SpiceDB is an open source database for scalably storing and querying fine-grained authorization data. Starting in version 1.35.0 and prior to version 1.37.1, clients that have enabled `LookupResources2` and have caveats in the evaluation path for their requests can return a permissionship of `CONDITIONAL` with context marked as missing, even then the context was supplied. LookupResources2 is the new default in SpiceDB 1.37.0 and has been opt-in since SpiceDB 1.35.0. The bug is patched as part of SpiceDB 1.37.1. As a workaround, disable LookupResources2 via the `--enable-experimental-lookup-resources` flag by setting it to `false`. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/authzed/spicedb | [] | [
"10616c73e4dfcebb282372ec8d4d878cf220ec94"
] |
CVE-2023-29193 | 2023-04-14T20:15:09 | 2025-01-15T04:50:27.446310 | SpiceDB is an open source, Google Zanzibar-inspired, database system for creating and managing security-critical application permissions. The `spicedb serve` command contains a flag named `--grpc-preshared-key` which is used to protect the gRPC API from being accessed by unauthorized requests. The values of this flag are to be considered sensitive, secret data. The `/debug/pprof/cmdline` endpoint served by the metrics service (defaulting running on port `9090`) reveals the command-line flags provided for debugging purposes. If a password is set via the `--grpc-preshared-key` then the key is revealed by this endpoint along with any other flags provided to the SpiceDB binary. This issue has been fixed in version 1.19.1.
### Impact
All deployments abiding by the recommended best practices for production usage are **NOT affected**:
- Authzed's SpiceDB Serverless
- Authzed's SpiceDB Dedicated
- SpiceDB Operator
Users configuring SpiceDB via environment variables are **NOT affected**.
Users **MAY be affected** if they expose their metrics port to an untrusted network and are configuring `--grpc-preshared-key` via command-line flag.
### Patches
TODO
### Workarounds
To workaround this issue you can do one of the following:
- Configure the preshared key via an environment variable (e.g. `SPICEDB_GRPC_PRESHARED_KEY=yoursecret spicedb serve`)
- Reconfigure the `--metrics-addr` flag to bind to a trusted network (e.g. `--metrics-addr=localhost:9090`)
- Disable the metrics service via the flag (e.g. `--metrics-enabled=false`)
- Adopt one of the recommended deployment models: [Authzed's managed services](https://authzed.com/pricing) or the [SpiceDB Operator](https://github.com/authzed/spicedb-operator)
### References
- [GitHub Security Advisory issued for SpiceDB](https://github.com/authzed/spicedb/security/advisories/GHSA-cjr9-mr35-7xh6)
- [Go issue #22085](https://github.com/golang/go/issues/22085) for documenting the risks of exposing pprof to the internet
- [Go issue #42834](https://github.com/golang/go/issues/42834) discusses preventing pprof registration to the default serve mux
- [semgrep rule go.lang.security.audit.net.pprof.pprof-debug-exposure](https://semgrep.dev/r?q=go.lang.security.audit.net.pprof) checks for a variation of this issue
### Credit
We'd like to thank Amit Laish, a security researcher at GE Vernova for responsibly disclosing this vulnerability.
| [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/authzed/spicedb | [] | [
"10616c73e4dfcebb282372ec8d4d878cf220ec94"
] |
CVE-2023-35930 | 2023-06-26T20:15:10 | 2025-02-19T03:32:39.684361 | SpiceDB is an open source, Google Zanzibar-inspired, database system for creating and managing security-critical application permissions. Any user making a negative authorization decision based on the results of a `LookupResources` request with 1.22.0 is affected. For example, using `LookupResources` to find a list of resources to allow access to be okay: some subjects that should have access to a resource may not. But if using `LookupResources` to find a list of banned resources instead, then some users that shouldn't have access may. Generally, `LookupResources` is not and should not be to gate access in this way - that's what the `Check` API is for. Additionally, version 1.22.0 has included a warning about this bug since its initial release. Users are advised to upgrade to version 1.22.2. Users unable to upgrade should avoid using `LookupResources` for negative authorization decisions. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/authzed/spicedb | [] | [
"10616c73e4dfcebb282372ec8d4d878cf220ec94"
] |
CVE-2023-46255 | 2023-10-31T16:15:10 | 2025-01-15T04:59:53.101322 | SpiceDB is an open source, Google Zanzibar-inspired database for creating and managing security-critical application permissions. Prior to version 1.27.0-rc1, when the provided datastore URI is malformed (e.g. by having a password which contains `:`) the full URI (including the provided password) is printed, so that the password is shown in the logs. Version 1.27.0-rc1 patches this issue. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/authzed/spicedb | [] | [
"10616c73e4dfcebb282372ec8d4d878cf220ec94"
] |
CVE-2022-21646 | 2022-01-11T22:15:07 | 2025-01-15T02:09:25.201043 | SpiceDB is a database system for managing security-critical application permissions. 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. In `v1.3.0`, the wildcard is ignored entirely in lookup's dispatch, resulting in the `banned` wildcard being ignored in the exclusion. Version 1.4.0 contains a patch for this issue. As a workaround, don't make use of wildcards on the right side of intersections or within exclusions. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/authzed/spicedb | [] | [
"10616c73e4dfcebb282372ec8d4d878cf220ec94"
] |
CVE-2020-10728 | 2022-08-16T21:15:09 | 2025-01-14T08:13:07.803352 | A flaw was found in automationbroker/apb container in versions up to and including 2.0.4-1. This container grants all users sudoer permissions allowing an unauthorized user with access to the running container the ability to escalate their own privileges. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/automationbroker/apb | [] | [
"77a4cd4036d7713c137ab931537933d226547cdf"
] |
CVE-2024-28056 | 2024-04-15T18:15:10 | 2025-01-15T05:11:26.661089 | Amazon AWS Amplify CLI before 12.10.1 incorrectly configures the role trust policy of IAM roles associated with Amplify projects. When the Authentication component is removed from an Amplify project, a Condition property is removed but "Effect":"Allow" remains present, and consequently sts:AssumeRoleWithWebIdentity would be available to threat actors with no conditions. Thus, if Amplify CLI had been used to remove the Authentication component from a project built between August 2019 and January 2024, an "assume role" may have occurred, and may have been leveraged to obtain unauthorized access to an organization's AWS resources. NOTE: the problem could only occur if an authorized AWS user removed an Authentication component. (The vulnerability did not give a threat actor the ability to remove an Authentication component.) However, in realistic situations, an authorized AWS user may have removed an Authentication component, e.g., if the objective were to stop using built-in Cognito resources, or move to a completely different identity provider. | null | https://github.com/aws-amplify/amplify-cli | [] | [
"89ae5ad77e7eb79e1d8c6a62b766963c574db49a"
] |
CVE-2022-23511 | 2022-12-12T13:15:12 | 2025-01-15T02:15:48.691281 | A privilege escalation issue exists within the Amazon CloudWatch Agent for Windows, software for collecting metrics and logs from Amazon EC2 instances and on-premises servers, in versions up to and including v1.247354. When users trigger a repair of the Agent, a pop-up window opens with SYSTEM permissions. Users with administrative access to affected hosts may use this to create a new command prompt as NT AUTHORITY\SYSTEM. To trigger this issue, the third party must be able to access the affected host and elevate their privileges such that they're able to trigger the agent repair process. They must also be able to install the tools required to trigger the issue. This issue does not affect the CloudWatch Agent for macOS or Linux. Agent users should upgrade to version 1.247355 of the CloudWatch Agent to address this issue. There is no recommended work around. Affected users must update the installed version of the CloudWatch Agent to address this issue. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-cloudwatch-agent | [] | [
"06b61c964ca2c3da640308ef1ae4727eaa4e009c"
] |
CVE-2019-13120 | 2019-10-07T22:15:10 | 2025-01-14T07:44:49.949257 | Amazon FreeRTOS up to and including v1.4.8 lacks length checking in prvProcessReceivedPublish, resulting in untargetable leakage of arbitrary memory contents on a device to an attacker. If an attacker has the authorization to send a malformed MQTT publish packet to an Amazon IoT Thing, which interacts with an associated vulnerable MQTT message in the application, specific circumstances could trigger this vulnerability. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-freertos | [] | [
"1fc5e966a0f8e541c0942bd02bb3504a4a6be9c6"
] |
CVE-2018-16601 | 2018-12-06T23:29:01 | 2025-01-14T07:25:08.291446 | An issue was discovered in Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Connect middleware TCP/IP component. A crafted IP header triggers a full memory space copy in prvProcessIPPacket, leading to denial of service and possibly remote code execution. | [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-freertos | [] | [
"1fc5e966a0f8e541c0942bd02bb3504a4a6be9c6"
] |
CVE-2018-16603 | 2018-12-06T23:29:01 | 2025-01-14T07:25:08.078205 | An issue was discovered in Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Connect middleware TCP/IP component. Out of bounds access to TCP source and destination port fields in xProcessReceivedTCPPacket can leak data back to an attacker. | [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-freertos | [] | [
"1fc5e966a0f8e541c0942bd02bb3504a4a6be9c6"
] |
CVE-2018-16526 | 2018-12-06T23:29:00 | 2025-01-14T07:25:09.827480 | Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Connect middleware TCP/IP component allow remote attackers to leak information or execute arbitrary code because of a Buffer Overflow during generation of a protocol checksum in usGenerateProtocolChecksum and prvProcessIPPacket. | [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-freertos | [] | [
"1fc5e966a0f8e541c0942bd02bb3504a4a6be9c6"
] |
CVE-2018-16598 | 2018-12-06T23:29:00 | 2025-01-14T07:25:11.101790 | An issue was discovered in Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Connect middleware TCP/IP component. In xProcessReceivedUDPPacket and prvParseDNSReply, any received DNS response is accepted, without confirming it matches a sent DNS request. | [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-freertos | [] | [
"1fc5e966a0f8e541c0942bd02bb3504a4a6be9c6"
] |
CVE-2018-16522 | 2018-12-06T23:29:00 | 2025-01-14T07:25:08.812333 | Amazon Web Services (AWS) FreeRTOS through 1.3.1 has an uninitialized pointer free in SOCKETS_SetSockOpt. | [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-freertos | [] | [
"1fc5e966a0f8e541c0942bd02bb3504a4a6be9c6"
] |
CVE-2018-16523 | 2018-12-06T23:29:00 | 2025-01-14T07:25:08.502029 | Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Connect middleware TCP/IP component allow division by zero in prvCheckOptions. | [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-freertos | [] | [
"1fc5e966a0f8e541c0942bd02bb3504a4a6be9c6"
] |
CVE-2018-16524 | 2018-12-06T23:29:00 | 2025-01-14T07:25:04.897994 | Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Connect middleware TCP/IP component allow information disclosure during parsing of TCP options in prvCheckOptions. | [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-freertos | [] | [
"1fc5e966a0f8e541c0942bd02bb3504a4a6be9c6"
] |
CVE-2018-16528 | 2018-12-06T23:29:00 | 2025-01-14T07:25:09.368278 | Amazon Web Services (AWS) FreeRTOS through 1.3.1 allows remote attackers to execute arbitrary code because of mbedTLS context object corruption in prvSetupConnection and GGD_SecureConnect_Connect in AWS TLS connectivity modules. | [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-freertos | [] | [
"1fc5e966a0f8e541c0942bd02bb3504a4a6be9c6"
] |
CVE-2018-16600 | 2018-12-06T23:29:00 | 2025-01-14T07:25:11.344069 | An issue was discovered in Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Connect middleware TCP/IP component. Out of bounds memory access during parsing of ARP packets in eARPProcessPacket can be used for information disclosure. | [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-freertos | [] | [
"1fc5e966a0f8e541c0942bd02bb3504a4a6be9c6"
] |
CVE-2018-16599 | 2018-12-06T23:29:00 | 2025-01-14T07:25:11.180096 | An issue was discovered in Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Connect middleware TCP/IP component. Out of bounds memory access during parsing of NBNS packets in prvTreatNBNS can be used for information disclosure. | [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-freertos | [] | [
"1fc5e966a0f8e541c0942bd02bb3504a4a6be9c6"
] |
CVE-2018-16602 | 2018-12-06T23:29:01 | 2025-01-14T07:25:08.872541 | An issue was discovered in Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Connect middleware TCP/IP component. Out of bounds memory access during parsing of DHCP responses in prvProcessDHCPReplies can be used for information disclosure. | [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-freertos | [] | [
"1fc5e966a0f8e541c0942bd02bb3504a4a6be9c6"
] |
CVE-2018-16525 | 2018-12-06T23:29:00 | 2025-01-14T07:25:08.416935 | Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Connect middleware TCP/IP component allow remote attackers to execute arbitrary code or leak information because of a Buffer Overflow during parsing of DNS\LLMNR packets in prvParseDNSReply. | [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-freertos | [] | [
"1fc5e966a0f8e541c0942bd02bb3504a4a6be9c6"
] |
CVE-2018-16527 | 2018-12-06T23:29:00 | 2025-01-14T07:25:09.876157 | Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Connect middleware TCP/IP component allow information disclosure during parsing of ICMP packets in prvProcessICMPPacket. | [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-freertos | [] | [
"1fc5e966a0f8e541c0942bd02bb3504a4a6be9c6"
] |
CVE-2022-29527 | 2022-04-20T10:15:08 | 2025-01-15T02:19:56.289989 | Amazon AWS amazon-ssm-agent before 3.1.1208.0 creates a world-writable sudoers file, which allows local attackers to inject Sudo rules and escalate privileges to root. This occurs in certain situations involving a race condition. | [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/aws/amazon-ssm-agent | [] | [
"8cbabacc74e68853bb42f10ddafdae10f2d33e6c"
] |
CVE-2024-45037 | 2024-08-27T19:15:17 | 2024-10-08T04:23:24.533045 | The AWS Cloud Development Kit (CDK) is an open-source framework for defining cloud infrastructure using code. Customers use it to create their own applications which are converted to AWS CloudFormation templates during deployment to a customer’s AWS account. CDK contains pre-built components called "constructs" that are higher-level abstractions providing defaults and best practices. This approach enables developers to use familiar programming languages to define complex cloud infrastructure more efficiently than writing raw CloudFormation templates. We identified an issue in AWS Cloud Development Kit (CDK) which, under certain conditions, can result in granting authenticated Amazon Cognito users broader than intended access. Specifically, if a CDK application uses the "RestApi" construct with "CognitoUserPoolAuthorizer" as the authorizer and uses authorization scopes to limit access. This issue does not affect the availability of the specific API resources. Authenticated Cognito users may gain unintended access to protected API resources or methods, leading to potential data disclosure, and modification issues. Impacted versions: >=2.142.0;<=2.148.0. A patch is included in CDK versions >=2.148.1. Users are advised to upgrade their AWS CDK version to 2.148.1 or newer and re-deploy their application(s) to address this issue. | null | https://github.com/aws/aws-cdk | [] | [
"ab288785279bf3d70ad3329e27ad1f6d2397942e"
] |
CVE-2023-35165 | 2023-06-23T21:15:09 | 2025-02-19T03:34:02.906462 | AWS Cloud Development Kit (AWS CDK) is an open-source software development framework to define cloud infrastructure in code and provision it through AWS CloudFormation. In the packages `aws-cdk-lib` 2.0.0 until 2.80.0 and `@aws-cdk/aws-eks` 1.57.0 until 1.202.0, `eks.Cluster` and `eks.FargateCluster` constructs create two roles, `CreationRole` and `default MastersRole`, that have an overly permissive trust policy.
The first, referred to as the `CreationRole`, is used by lambda handlers to create the cluster and deploy Kubernetes resources (e.g `KubernetesManifest`, `HelmChart`, ...) onto it. Users with CDK version higher or equal to 1.62.0 (including v2 users) may be affected.
The second, referred to as the `default MastersRole`, is provisioned only if the `mastersRole` property isn't provided and has permissions to execute `kubectl` commands on the cluster. Users with CDK version higher or equal to 1.57.0 (including v2 users) may be affected.
The issue has been fixed in `@aws-cdk/aws-eks` v1.202.0 and `aws-cdk-lib` v2.80.0. These versions no longer use the account root principal. Instead, they restrict the trust policy to the specific roles of lambda handlers that need it. There is no workaround available for CreationRole. To avoid creating the `default MastersRole`, use the `mastersRole` property to explicitly provide a role. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/aws/aws-cdk | [] | [
"ab288785279bf3d70ad3329e27ad1f6d2397942e"
] |
CVE-2023-49091 | 2023-11-29T20:15:08 | 2025-01-22T08:49:46.784026 | Cosmos provides users the ability self-host a home server by acting as a secure gateway to your application, as well as a server manager. Cosmos-server is vulnerable due to to the authorization header used for user login remaining valid and not expiring after log out. This vulnerability allows an attacker to use the token to gain unauthorized access to the application/system even after the user has logged out. This issue has been patched in version 0.13.1. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/azukaar/cosmos-server | [] | [
"281c8c1ea434539a71d4add025ed3cc09657d63c"
] |
CVE-2025-23214 | 2025-01-20T18:15:14 | 2025-01-21T02:12:05.712913 | Cosmos provides users the ability self-host a home server by acting as a secure gateway to your application, as well as a server manager. By monitoring the error code returned in the login, it is possible to figure out whether a user exist or not in the database. Patched in 0.17.7. | null | https://github.com/azukaar/cosmos-server | [] | [
"281c8c1ea434539a71d4add025ed3cc09657d63c"
] |
CVE-2022-23551 | 2022-12-21T20:15:09 | 2025-01-15T02:15:45.801133 | aad-pod-identity assigns Azure Active Directory identities to Kubernetes applications and has now been deprecated as of 24 October 2022. The NMI component in AAD Pod Identity intercepts and validates token requests based on regex. In this case, a token request made with backslash in the request (example: `/metadata/identity\oauth2\token/`) would bypass the NMI validation and be sent to IMDS allowing a pod in the cluster to access identities that it shouldn't have access to. This issue has been fixed and has been included in AAD Pod Identity release version 1.8.13. If using the AKS pod-managed identities add-on, no action is required. The clusters should now be running the version 1.8.13 release. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L",
"type": "CVSS_V3"
}
] | https://github.com/azure/aad-pod-identity | [] | [
"7b1eaabf3eb97032264aa7aef38cb9331c973114"
] |
CVE-2020-8567 | 2021-01-21T17:15:14 | 2025-01-14T08:49:21.508955 | Kubernetes Secrets Store CSI Driver Vault Plugin prior to v0.0.6, Azure Plugin prior to v0.0.10, and GCP Plugin prior to v0.2.0 allow an attacker who can create specially-crafted SecretProviderClass objects to write to arbitrary file paths on the host filesystem, including /var/lib/kubelet/pods. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/azure/secrets-store-csi-driver-provider-azure | [] | [
"21fe08c62b1ea1ca5b6f265cf7d21c7a2d8f761d"
] |
CVE-2024-29183 | 2024-04-19T16:15:10 | 2025-01-15T05:11:40.989158 | OpenRASP is a RASP solution that directly integrates its protection engine into the application server by instrumentation. There exists a reflected XSS in the /login page due to a reflection of the redirect parameter. This allows an attacker to execute arbitrary javascript with the permissions of a user after the user logins with their account. | null | https://github.com/baidu/openrasp | [] | [
"a0634d6ea7c170284c262c757e56a7e5a8f242d0"
] |
CVE-2021-32825 | 2021-08-16T19:15:14 | 2025-01-15T01:54:45.577228 | bblfshd is an open source self-hosted server for source code parsing. In bblfshd before commit 4265465b9b6fb5663c30ee43806126012066aad4 there is a "zipslip" vulnerability. The unsafe handling of symbolic links in an unpacking routine may enable attackers to read and/or write to arbitrary locations outside the designated target folder. This issue may lead to arbitrary file write (with same permissions as the program running the unpack operation) if the attacker can control the archive file. Additionally, if the attacker has read access to the unpacked files, he may be able to read arbitrary system files the parent process has permissions to read. For more details including a PoC see the referenced GHSL-2020-258. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/bblfsh/bblfshd | [] | [
"7f9598f689b6a0e9bbc228e056abc08d23604597"
] |
CVE-2024-40465 | 2024-07-31T21:15:17 | 2024-10-08T04:19:20.589767 | An issue in beego v.2.2.0 and before allows a remote attacker to escalate privileges via the getCacheFileName function in file.go file | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/beego/beego | [] | [
"c0d9d883c8005d9b8f231a3497a4ff09636359d4"
] |
CVE-2024-40464 | 2024-07-31T21:15:17 | 2024-10-08T04:19:18.285864 | An issue in beego v.2.2.0 and before allows a remote attacker to escalate privileges via the sendMail function located in beego/core/logs/smtp.go file | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/beego/beego | [] | [
"c0d9d883c8005d9b8f231a3497a4ff09636359d4"
] |
CVE-2024-55885 | 2024-12-12T20:15:21 | 2025-01-15T05:16:38.866676 | beego is an open-source web framework for the Go programming language. Versions of beego prior to 2.3.4 use MD5 as a hashing algorithm. MD5 is no longer considered secure against well-funded opponents due to its vulnerability to collision attacks. Version 2.3.4 replaces MD5 with SHA256. | null | https://github.com/beego/beego | [] | [
"c0d9d883c8005d9b8f231a3497a4ff09636359d4"
] |
CVE-2021-39391 | 2021-09-14T18:15:08 | 2025-01-14T09:31:37.533670 | Cross Site Scripting (XSS) vulnerability exists in the admin panel in Beego v2.0.1 via the URI path in an HTTP request, which is activated by administrators viewing the "Request Statistics" page. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/beego/beego | [] | [
"c0d9d883c8005d9b8f231a3497a4ff09636359d4"
] |
CVE-2021-30080 | 2022-04-05T16:15:12 | 2025-01-15T01:52:02.704684 | An issue was discovered in the route lookup process in beego before 1.12.11 that allows attackers to bypass access control. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/beego/beego | [] | [
"c0d9d883c8005d9b8f231a3497a4ff09636359d4"
] |
CVE-2022-31836 | 2022-07-05T15:15:08 | 2025-01-14T10:59:44.803598 | The leafInfo.match() function in Beego v2.0.3 and below uses path.join() to deal with wildcardvalues which can lead to cross directory risk. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/beego/beego | [] | [
"c0d9d883c8005d9b8f231a3497a4ff09636359d4"
] |
CVE-2024-41254 | 2024-07-31T21:15:17 | 2025-02-19T03:38:14.434344 | An issue was discovered in litestream v0.3.13. The usage of the ssh.InsecureIgnoreHostKey() disables host key verification, possibly allowing attackers to obtain sensitive information via a man-in-the-middle attack. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/benbjohnson/litestream | [] | [
"977d4a5ee45ae546537324a3cfbf926de3bebc97"
] |
CVE-2022-45933 | 2022-11-27T03:15:11 | 2025-01-14T11:15:33.816151 | KubeView through 0.1.31 allows attackers to obtain control of a Kubernetes cluster because api/scrape/kube-system does not require authentication, and retrieves certificate files that can be used for authentication as kube-admin. NOTE: the vendor's position is that KubeView was a "fun side project and a learning exercise," and not "very secure." | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/benc-uk/kubeview | [] | [
"a00a7d942805047ddeae4b264ce14ac2fe9d9487"
] |
CVE-2024-2912 | 2024-04-16T00:15:11 | 2025-01-15T05:11:32.531014 | An insecure deserialization vulnerability exists in the BentoML framework, allowing remote code execution (RCE) by sending a specially crafted POST request. By exploiting this vulnerability, attackers can execute arbitrary commands on the server hosting the BentoML application. The vulnerability is triggered when a serialized object, crafted to execute OS commands upon deserialization, is sent to any valid BentoML endpoint. This issue poses a significant security risk, enabling attackers to compromise the server and potentially gain unauthorized access or control. | null | https://github.com/bentoml/bentoml | [] | [
"da08bfabb0805f01079f8bd176e22b3658a780eb"
] |
CVE-2020-12118 | 2020-04-23T22:15:12 | 2025-01-14T08:15:36.071443 | The keygen protocol implementation in Binance tss-lib before 1.2.0 allows attackers to generate crafted h1 and h2 parameters in order to compromise a signing round or obtain sensitive information from other parties. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/binance-chain/tss-lib | [] | [
"4fcd04b0ce5527ece51afa70c7852b5fd03b120c"
] |
CVE-2022-31053 | 2022-06-13T20:15:07 | 2025-01-14T10:58:23.610020 | Biscuit is an authentication and authorization token for microservices architectures. The Biscuit specification version 1 contains a vulnerable algorithm that allows malicious actors to forge valid Γ-signatures. Such an attack would allow an attacker to create a token with any access level. The version 2 of the specification mandates a different algorithm than gamma signatures and as such is not affected by this vulnerability. The Biscuit implementations in Rust, Haskell, Go, Java and Javascript all have published versions following the v2 specification. There are no known workarounds for this issue. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/biscuit-auth/biscuit-go | [] | [
"9762ea334b1c190ee7c769b8741616bca5df546d"
] |
CVE-2024-41111 | 2024-07-18T23:15:02 | 2025-01-15T05:15:48.056992 | Sliver is an open source cross-platform adversary emulation/red team framework, it can be used by organizations of all sizes to perform security testing. Sliver version 1.6.0 (prerelease) is vulnerable to RCE on the teamserver by a low-privileged "operator" user. The RCE is as the system root user. The exploit is pretty fun as we make the Sliver server pwn itself. As described in a past issue (#65), "there is a clear security boundary between the operator and server, an operator should not inherently be able to run commands or code on the server." An operator who exploited this vulnerability would be able to view all console logs, kick all other operators, view and modify files stored on the server, and ultimately delete the server. This issue has not yet be addressed but is expected to be resolved before the full release of version 1.6.0. Users of the 1.6.0 prerelease should avoid using Silver in production. | null | https://github.com/bishopfox/sliver | [] | [
"af46878f8520c0c65bbb1e80d813a9658ba09188"
] |
CVE-2023-34758 | 2023-08-28T12:15:09 | 2025-02-19T03:32:40.929256 | Sliver from v1.5.x to v1.5.39 has an improper cryptographic implementation, which allows attackers to execute a man-in-the-middle attack via intercepted and crafted responses. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/bishopfox/sliver | [] | [
"af46878f8520c0c65bbb1e80d813a9658ba09188"
] |
CVE-2025-27090 | 2025-02-19T22:15:24 | 2025-02-20T08:55:24.871543 | Sliver is an open source cross-platform adversary emulation/red team framework, it can be used by organizations of all sizes to perform security testing. The reverse port forwarding in sliver teamserver allows the implant to open a reverse tunnel on the sliver teamserver without verifying if the operator instructed the implant to do so. The only impact that has been shown is the exposure of the server's IP address to a third party. This issue has been addressed in version 1.5.43 and all users are advised to upgrade. There are no known workarounds for this vulnerability. | null | https://github.com/bishopfox/sliver | [] | [
"af46878f8520c0c65bbb1e80d813a9658ba09188"
] |
CVE-2017-1000070 | 2017-07-17T13:18:18 | 2025-01-14T06:55:52.695042 | 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 | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/bitly/oauth2_proxy | [] | [
"a66f7c50eac53b23d10657b64cc133364d452aea"
] |
CVE-2017-1000069 | 2017-07-17T13:18:18 | 2025-01-14T06:55:50.797193 | CSRF in Bitly oauth2_proxy 2.1 during authentication flow | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/bitly/oauth2_proxy | [] | [
"a66f7c50eac53b23d10657b64cc133364d452aea"
] |
CVE-2023-0247 | 2023-01-12T17:15:09 | 2025-01-15T04:37:01.639377 | Uncontrolled Search Path Element in GitHub repository bits-and-blooms/bloom prior to 3.3.1. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/bits-and-blooms/bloom | [] | [
"cb9965b1435d69b572099401455a1308db0478da"
] |
CVE-2022-0071 | 2022-04-19T23:15:13 | 2025-01-14T09:08:47.336879 | Incomplete fix for CVE-2021-3101. Hotdog, prior to v1.0.2, did not mimic the resource limits, device restrictions, or syscall filters of the target JVM process. This would allow a container to exhaust the resources of the host, modify devices, or make syscalls that would otherwise be blocked. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/bottlerocket-os/hotdog | [] | [
"c32a7572e104d88e96ce2e6fbfb168387d289c80"
] |
CVE-2021-3101 | 2022-04-19T23:15:13 | 2025-01-14T09:12:06.532801 | Hotdog, prior to v1.0.1, did not mimic the capabilities or the SELinux label of the target JVM process. This would allow a container to gain full privileges on the host, bypassing restrictions set on the container. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/bottlerocket-os/hotdog | [] | [
"c32a7572e104d88e96ce2e6fbfb168387d289c80"
] |
CVE-2022-39304 | 2022-12-20T20:15:10 | 2025-01-15T02:34:49.227573 | ghinstallation provides transport, which implements http.RoundTripper to provide authentication as an installation for GitHub Apps. In ghinstallation version 1, when the request to refresh an installation token failed, the HTTP request and response would be returned for debugging. The request contained the bearer JWT for the App, and was returned back to clients. This token is short lived (10 minute maximum). This issue has been patched and is available in version 2.0.0.
| [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/bradleyfalzon/ghinstallation | [] | [
"24e56b3fb7669f209134a01eff731d7e2ef72a5c"
] |
CVE-2019-3818 | 2019-02-05T17:29:00 | 2025-01-14T08:00:54.419204 | The kube-rbac-proxy container before version 0.4.1 as used in Red Hat OpenShift Container Platform does not honor TLS configurations, allowing for use of insecure ciphers and TLS 1.0. An attacker could target traffic sent over a TLS connection with a weak configuration and potentially break the encryption. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/brancz/kube-rbac-proxy | [] | [
"7d54c310ddf7f07a29745eec0665f46977236d0a"
] |
CVE-2022-39219 | 2022-09-26T14:15:10 | 2025-01-14T11:06:27.388199 | Bifrost is a middleware package which can synchronize MySQL/MariaDB binlog data to other types of databases. Versions 1.8.6-release and prior are vulnerable to authentication bypass when using HTTP basic authentication. This may allow group members who only have read permissions to write requests when they are normally forbidden from doing so. Version 1.8.7-release contains a patch. There are currently no known workarounds. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/brokercap/bifrost | [] | [
"73956dbc64c2c2f068a56b5b5f0ba57df60ad5a3"
] |
CVE-2022-39267 | 2022-10-19T13:15:08 | 2025-01-14T11:06:46.217358 | Bifrost is a heterogeneous middleware that synchronizes MySQL, MariaDB to Redis, MongoDB, ClickHouse, MySQL and other services for production environments. Versions prior to 1.8.8-release are subject to authentication bypass in the admin and monitor user groups by deleting the X-Requested-With: XMLHttpRequest field in the request header. This issue has been patched in 1.8.8-release. There are no known workarounds. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/brokercap/bifrost | [] | [
"73956dbc64c2c2f068a56b5b5f0ba57df60ad5a3"
] |
CVE-2024-34478 | 2024-05-05T01:15:06 | 2025-02-19T03:36:21.730303 | btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of funds. | null | https://github.com/btcsuite/btcd | [] | [
"0f49e1000633b0af6d7bbef97d69671f4c99e37e"
] |
CVE-2024-38365 | 2024-10-11T20:15:04 | 2024-10-15T19:12:16.022529 | btcd is an alternative full node bitcoin implementation written in Go (golang). The btcd Bitcoin client (versions 0.10 to 0.24) did not correctly re-implement Bitcoin Core's "FindAndDelete()" functionality. This logic is consensus-critical: the difference in behavior with the other Bitcoin clients can lead to btcd clients accepting an invalid Bitcoin block (or rejecting a valid one). This consensus failure can be leveraged to cause a chain split (accepting an invalid Bitcoin block) or be exploited to DoS the btcd nodes (rejecting a valid Bitcoin block). An attacker can create a standard transaction where FindAndDelete doesn't return a match but removeOpCodeByData does making btcd get a different sighash, leading to a chain split. Importantly, this vulnerability can be exploited remotely by any Bitcoin user and does not require any hash power. This is because the difference in behavior can be triggered by a "standard" Bitcoin transaction, that is a transaction which gets relayed through the P2P network before it gets included in a Bitcoin block. `removeOpcodeByData(script []byte, dataToRemove []byte)` removes any data pushes from `script` that contain `dataToRemove`. However, `FindAndDelete` only removes exact matches. So for example, with `script = "<data> <data||foo>"` and `dataToRemove = "data"` btcd will remove both data pushes but Bitcoin Core's `FindAndDelete` only removes the first `<data>` push. This has been patched in btcd version v0.24.2. Users are advised to upgrade. There are no known workarounds for this issue. | null | https://github.com/btcsuite/btcd | [] | [
"0f49e1000633b0af6d7bbef97d69671f4c99e37e"
] |
CVE-2022-39389 | 2022-11-17T22:15:10 | 2025-02-19T03:29:46.028671 | Lightning Network Daemon (lnd) is an implementation of a lightning bitcoin overlay network node. All lnd nodes before version `v0.15.4` are vulnerable to a block parsing bug that can cause a node to enter a degraded state once encountered. In this degraded state, nodes can continue to make payments and forward HTLCs, and close out channels. Opening channels is prohibited, and also on chain transaction events will be undetected. This can cause loss of funds if a CSV expiry is researched during a breach attempt or a CLTV delta expires forgetting the funds in the HTLC. A patch is available in `lnd` version 0.15.4. Users are advised to upgrade. Users unable to upgrade may use the `lncli updatechanpolicy` RPC call to increase their CLTV value to a very high amount or increase their fee policies. This will prevent nodes from routing through your node, meaning that no pending HTLCs can be present. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L",
"type": "CVSS_V3"
}
] | https://github.com/btcsuite/btcd | [] | [
"0f49e1000633b0af6d7bbef97d69671f4c99e37e"
] |
CVE-2022-44797 | 2022-11-07T04:15:09 | 2025-02-19T03:28:39.125753 | btcd before 0.23.2, as used in Lightning Labs lnd before 0.15.2-beta and other Bitcoin-related products, mishandles witness size checking. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/btcsuite/btcd | [] | [
"0f49e1000633b0af6d7bbef97d69671f4c99e37e"
] |
CVE-2024-25431 | 2024-11-08T17:15:06 | 2024-11-15T07:49:49.226253 | An issue in bytecodealliance wasm-micro-runtime before v.b3f728c and fixed in commit 06df58f allows a remote attacker to escalate privileges via a crafted file to the check_was_abi_compatibility function. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/bytecodealliance/wasm-micro-runtime | [] | [
"fa2f29fd8ab3f72e3efb551d19cb6b214ead91f8"
] |
CVE-2023-48105 | 2023-11-22T23:15:10 | 2025-01-14T12:04:38.565455 | An heap overflow vulnerability was discovered in Bytecode alliance wasm-micro-runtime v.1.2.3 allows a remote attacker to cause a denial of service via the wasm_loader_prepare_bytecode function in core/iwasm/interpreter/wasm_loader.c. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/bytecodealliance/wasm-micro-runtime | [] | [
"fa2f29fd8ab3f72e3efb551d19cb6b214ead91f8"
] |
CVE-2023-52284 | 2023-12-31T06:15:08 | 2025-01-14T12:07:45.733151 | Bytecode Alliance wasm-micro-runtime (aka WebAssembly Micro Runtime or WAMR) before 1.3.0 can have an "double free or corruption" error for a valid WebAssembly module because push_pop_frame_ref_offset is mishandled. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/bytecodealliance/wasm-micro-runtime | [] | [
"fa2f29fd8ab3f72e3efb551d19cb6b214ead91f8"
] |
CVE-2019-18923 | 2019-11-13T22:15:12 | 2025-01-14T07:52:10.209343 | Insufficient content type validation of proxied resources in go-camo before 2.1.1 allows a remote attacker to serve arbitrary content from go-camo's origin. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cactus/go-camo | [] | [
"8e89977547051a4e2f28a2c8aece9ac020423289"
] |
CVE-2019-14255 | 2019-08-08T13:15:12 | 2025-01-14T07:46:14.435591 | A Server Side Request Forgery (SSRF) vulnerability in go-camo up to version 1.1.4 allows a remote attacker to perform HTTP requests to internal endpoints. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cactus/go-camo | [] | [
"8e89977547051a4e2f28a2c8aece9ac020423289"
] |
CVE-2022-1883 | 2022-05-25T09:15:08 | 2025-01-15T02:13:38.742811 | SQL Injection in GitHub repository camptocamp/terraboard prior to 2.2.0. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/camptocamp/terraboard | [] | [
"06ff551cf5ba489bd52712b8f02d98e7add86e26"
] |
CVE-2016-1582 | 2016-06-09T16:59:03 | 2025-01-14T06:22:48.486353 | LXD before 2.0.2 does not properly set permissions when switching an unprivileged container into privileged mode, which allows local users to access arbitrary world readable paths in the container directory via unspecified vectors. | [
{
"score": "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/canonical/lxd | [] | [
"7d65940b33f106b7baecb64e7bb19509db5cfd0b"
] |
CVE-2016-1581 | 2016-06-09T16:59:01 | 2025-01-14T06:22:48.365114 | LXD before 2.0.2 uses world-readable permissions for /var/lib/lxd/zfs.img when setting up a loop based ZFS pool, which allows local users to copy and read data from arbitrary containers via unspecified vectors. | [
{
"score": "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/canonical/lxd | [] | [
"7d65940b33f106b7baecb64e7bb19509db5cfd0b"
] |
CVE-2024-3250 | 2024-04-04T15:15:39 | 2025-02-19T02:50:39.690616 | It was discovered that Canonical's Pebble service manager read-file API and the associated pebble pull command, before v1.10.2, allowed unprivileged local users to read files with root-equivalent permissions when Pebble was running as root. Fixes are also available as backports to v1.1.1, v1.4.2, and v1.7.4. | null | https://github.com/canonical/pebble | [] | [
"a84efd8950d50e1e7f90952700e8e8ac6b57b32f"
] |
CVE-2024-6714 | 2024-07-23T16:15:06 | 2025-01-15T05:17:10.748297 | An issue was discovered in provd before version 0.1.5 with a setuid binary, which allows a local attacker to escalate their privilege. | null | https://github.com/canonical/ubuntu-desktop-provision | [] | [
"cce89bc3f5c32441adc632d43595aac511e7942c"
] |
CVE-2023-4564 | 2023-10-03T16:15:10 | 2025-01-14T12:02:11.110676 | This vulnerability could allow an attacker to store a malicious JavaScript payload in the broadcast message parameter within the admin panel. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/capensis/canopsis | [] | [
"7cd81a363e98107a6fc6c660fa52f2cfdbeb6348"
] |
CVE-2023-3196 | 2023-10-03T16:15:10 | 2025-01-14T10:43:22.740762 | This vulnerability could allow an attacker to store a malicious JavaScript payload in the login footer and login page description parameters within the administration panel. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/capensis/canopsis | [] | [
"7cd81a363e98107a6fc6c660fa52f2cfdbeb6348"
] |
CVE-2024-41264 | 2024-08-01T16:15:06 | 2025-02-19T03:38:18.699679 | An issue discovered in casdoor v1.636.0 allows attackers to obtain sensitive information via the ssh.InsecureIgnoreHostKey() method. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/casdoor/casdoor | [] | [
"051752340d21470db4020b9cf1b46fa50ae908a9"
] |
CVE-2023-34927 | 2023-06-22T13:15:10 | 2025-02-19T03:32:33.166889 | Casdoor v1.331.0 and below was discovered to contain a Cross-Site Request Forgery (CSRF) in the endpoint /api/set-password. This vulnerability allows attackers to arbitrarily change the victim user's password via supplying a crafted URL. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/casdoor/casdoor | [] | [
"051752340d21470db4020b9cf1b46fa50ae908a9"
] |
CVE-2022-24124 | 2022-01-29T23:15:07 | 2025-02-19T03:24:06.578752 | The query API in Casdoor before 1.13.1 has a SQL injection vulnerability related to the field and value parameters, as demonstrated by api/get-organizations. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/casdoor/casdoor | [] | [
"051752340d21470db4020b9cf1b46fa50ae908a9"
] |
CVE-2022-38638 | 2022-09-09T20:15:11 | 2025-02-19T03:29:34.951657 | Casdoor v1.97.3 was discovered to contain an arbitrary file write vulnerability via the fullFilePath parameter at /api/upload-resource. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/casdoor/casdoor | [] | [
"051752340d21470db4020b9cf1b46fa50ae908a9"
] |
CVE-2022-44942 | 2022-12-07T02:15:09 | 2025-02-19T03:28:32.825984 | Casdoor before v1.126.1 was discovered to contain an arbitrary file deletion vulnerability via the uploadFile function. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/casdoor/casdoor | [] | [
"051752340d21470db4020b9cf1b46fa50ae908a9"
] |
CVE-2021-3810 | 2021-09-17T07:15:09 | 2025-02-19T03:20:44.428620 | code-server is vulnerable to Inefficient Regular Expression Complexity | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cdr/code-server | [] | [
"911af4075f111f5c47700fbc731978bb65941a56"
] |
CVE-2021-42648 | 2022-05-11T18:15:23 | 2025-02-19T03:21:42.540149 | Cross-site scripting (XSS) vulnerability exists in Coder Code-Server before 3.12.0, allows attackers to execute arbitrary code via crafted URL. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cdr/code-server | [] | [
"911af4075f111f5c47700fbc731978bb65941a56"
] |
CVE-2024-34713 | 2024-05-14T16:17:27 | 2025-01-15T05:13:56.450239 | sshproxy is used on a gateway to transparently proxy a user SSH connection on the gateway to an internal host via SSH. Prior to version 1.6.3, any user authorized to connect to a ssh server using `sshproxy` can inject options to the `ssh` command executed by `sshproxy`. All versions of `sshproxy` are impacted. The problem is patched starting in version 1.6.3. The only workaround is to use the `force_command` option in `sshproxy.yaml`, but it's rarely relevant. | null | https://github.com/cea-hpc/sshproxy | [] | [
"62fc70e40562c0e70573661ec686b0e28098b008"
] |
CVE-2023-49552 | 2024-01-02T23:15:12 | 2025-01-14T12:06:13.201034 | An Out of Bounds Write in Cesanta mjs 2.20.0 allows a remote attacker to cause a denial of service via the mjs_op_json_stringify function in the msj.c file. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2023-49551 | 2024-01-02T23:15:12 | 2025-01-14T12:06:12.722016 | An issue in Cesanta mjs 2.20.0 allows a remote attacker to cause a denial of service via the mjs_op_json_parse function in the msj.c file. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2023-49553 | 2024-01-02T23:15:12 | 2025-01-14T12:06:12.443972 | An issue in Cesanta mjs 2.20.0 allows a remote attacker to cause a denial of service via the mjs_destroy function in the msj.c file. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2023-49549 | 2024-01-02T23:15:12 | 2025-01-14T12:06:12.968714 | An issue in Cesanta mjs 2.20.0 allows a remote attacker to cause a denial of service via the mjs_getretvalpos function in the msj.c file. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2023-49550 | 2024-01-02T23:15:12 | 2025-01-14T12:06:13.126070 | An issue in Cesanta mjs 2.20.0 allows a remote attacker to cause a denial of service via the mjs+0x4ec508 component. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2023-29571 | 2023-04-12T15:15:13 | 2025-02-08T04:45:36.081929 | Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via gc_sweep at src/mjs_gc.c. This vulnerability can lead to a Denial of Service (DoS). | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2023-29569 | 2023-04-14T12:15:07 | 2025-02-06T23:51:37.819278 | Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via ffi_cb_impl_wpwwwww at src/mjs_ffi.c. This vulnerability can lead to a Denial of Service (DoS). | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2023-29570 | 2023-04-24T14:15:07 | 2025-02-04T19:58:40.062361 | Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via mjs_ffi_cb_free at src/mjs_ffi.c. This vulnerability can lead to a Denial of Service (DoS). | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2023-43338 | 2023-09-23T00:15:20 | 2025-01-14T11:59:38.882048 | Cesanta mjs v2.20.0 was discovered to contain a function pointer hijacking vulnerability via the function mjs_get_ptr(). This vulnerability allows attackers to execute arbitrary code via a crafted input. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2021-36535 | 2023-02-03T18:15:10 | 2025-01-14T09:24:26.467412 | Buffer Overflow vulnerability in Cesanta mJS 1.26 allows remote attackers to cause a denial of service via crafted .js file to mjs_set_errorf. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2023-30088 | 2023-05-09T16:15:14 | 2025-01-29T23:49:59.514502 | An issue found in Cesanta MJS v.1.26 allows a local attacker to cause a denial of service via the mjs_execute function in mjs.c. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2023-30087 | 2023-05-09T16:15:14 | 2025-01-29T17:48:32.790935 | Buffer Overflow vulnerability found in Cesanta MJS v.1.26 allows a local attacker to cause a denial of service via the mjs_mk_string function in mjs.c. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2020-36368 | 2021-05-28T21:15:08 | 2025-01-14T08:46:06.320227 | Stack overflow vulnerability in parse_statement Cesanta MJS 1.20.1, allows remote attackers to cause a Denial of Service (DoS) via a crafted file. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2020-18392 | 2021-05-28T21:15:08 | 2025-01-14T08:35:51.471897 | Stack overflow vulnerability in parse_array Cesanta MJS 1.20.1, allows remote attackers to cause a Denial of Service (DoS) via a crafted file. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [
"CWE-674"
] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2020-36369 | 2021-05-28T21:15:08 | 2025-01-14T08:46:06.469668 | Stack overflow vulnerability in parse_statement_list Cesanta MJS 1.20.1, allows remote attackers to cause a Denial of Service (DoS) via a crafted file. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2020-36370 | 2021-05-28T21:15:08 | 2025-01-14T08:46:07.285555 | Stack overflow vulnerability in parse_unary Cesanta MJS 1.20.1, allows remote attackers to cause a Denial of Service (DoS) via a crafted file. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2020-36366 | 2021-05-28T21:15:08 | 2025-01-14T08:46:04.317262 | Stack overflow vulnerability in parse_value Cesanta MJS 1.20.1, allows remote attackers to cause a Denial of Service (DoS) via a crafted file. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2020-36374 | 2021-05-28T21:15:08 | 2025-01-14T08:46:06.944035 | Stack overflow vulnerability in parse_comparison Cesanta MJS 1.20.1, allows remote attackers to cause a Denial of Service (DoS) via a crafted file. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2020-36371 | 2021-05-28T21:15:08 | 2025-01-14T08:46:06.582180 | Stack overflow vulnerability in parse_mul_div_rem Cesanta MJS 1.20.1, allows remote attackers to cause a Denial of Service (DoS) via a crafted file. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
CVE-2020-36373 | 2021-05-28T21:15:08 | 2025-01-14T08:46:07.447961 | Stack overflow vulnerability in parse_shifts Cesanta MJS 1.20.1, allows remote attackers to cause a Denial of Service (DoS) via a crafted file. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cesanta/mjs | [] | [
"2827bd00b59bdc176a010b22fc4acde9b580d6c2"
] |
Subsets and Splits