Overview 14 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
14matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
2
14.3%
Not applicable
12
85.7%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
14
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
1
7.1%
Forecast only
0
0.0%
No public exploit
13
92.9%
split by
peak 10 / year
201710
Not applicable10
High5
Medium5
not blocked10
No public exploit10
20182
Outside Waratek scope1
Not applicable1
High1
Medium1
not blocked2
No public exploit2
20190
20200
20210
20221
Outside Waratek scope1
Medium1
not blocked1
Proof of concept only1
20230
20241
Not applicable1
High1
not blocked1
No public exploit1
20172018201920202021202220232024
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-7143 | High | 2024-08-07 | Not applicable | No public exploit | A flaw was found in the Pulp package. When a role-based access control (RBAC) object in Pulp is set to assign permissions on its creation, it uses the `AutoAddObjPermsMixin` (typically the add_roles_for_object_creator method). This method finds the object creator by checking the current authenticated user. For objects that are created within a task, this current user is set by the first user with any permissions on the task object. This means the oldest user with model/domain-level task permissions will always be set as the current user of a task, even if they didn't dispatch the task. Therefore, all objects created in tasks will have their permissions assigned to this oldest user, and the creating user will receive nothing. |
| CVE-2022-3644 | Medium | 2022-10-25 | Outside Waratek scope | Proof of concept only | The collection remote for pulp_ansible stores tokens in plaintext instead of using pulp's encrypted field and exposes them in read/write mode via the API () instead of marking it as write only. |
| CVE-2018-10917 | Medium | 2018-08-15 | Not applicable | No public exploit | pulp 2.16.x and possibly older is vulnerable to an improper path parsing. A malicious user or a malicious iso feed repository can write to locations accessible to the 'apache' user. This may lead to overwrite of published content on other iso repositories. |
| CVE-2018-1090 | High | 2018-06-18 | Outside Waratek scope | No public exploit | In Pulp before version 2.16.2, secrets are passed into override_config when triggering a task and then become readable to all users with read access on the distributor/importer. An attacker with API access can then view these secrets. |
| CVE-2015-5263 | High | 2017-09-25 | Not applicable | No public exploit | pulp-consumer-client 2.4.0 through 2.6.3 does not check the server's TLS certificate signatures when retrieving the server's public key upon registration. |
| CVE-2016-3704 | High | 2017-06-13 | Not applicable | No public exploit | Pulp before 2.8.5 uses bash's $RANDOM in an unsafe way to generate passwords. |
| CVE-2016-3696 | Medium | 2017-06-13 | Not applicable | No public exploit | The pulp-qpid-ssl-cfg script in Pulp before 2.8.5 allows local users to obtain the CA key. |
| CVE-2016-3112 | High | 2017-06-08 | Not applicable | No public exploit | client/consumer/cli.py in Pulp before 2.8.3 writes consumer private keys to etc/pki/pulp/consumer/consumer-cert.pem as world-readable, which allows remote authenticated users to obtain the consumer private keys and escalate privileges by reading /etc/pki/pulp/consumer/consumer-cert, and authenticating as a consumer user. |
| CVE-2016-3111 | Medium | 2017-06-08 | Not applicable | No public exploit | pulp.spec in the installation process for Pulp 2.8.3 generates the RSA key pairs used to validate messages between the pulp server and pulp consumers in a directory that is world-readable before later modifying the permissions, which might allow local users to read the generated RSA keys via reading the key files while the installation process is running. |
| CVE-2016-3108 | High | 2017-06-08 | Not applicable | No public exploit | The pulp-gen-nodes-certificate script in Pulp before 2.8.3 allows local users to leak the keys or write to arbitrary files via a symlink attack. |
| CVE-2016-3107 | Medium | 2017-06-08 | Not applicable | No public exploit | The Node certificate in Pulp before 2.8.3 contains the private key, and is stored in a world-readable file in the "/etc/pki/pulp/nodes/" directory, which allows local users to gain access to sensitive data. |
| CVE-2016-3095 | Medium | 2017-06-08 | Not applicable | No public exploit | server/bin/pulp-gen-ca-certificate in Pulp before 2.8.2 allows local users to read the generated private key. |
| CVE-2016-3106 | Medium | 2017-04-13 | Not applicable | No public exploit | Pulp before 2.8.3 creates a temporary directory during CA key generation in an insecure manner. |
| CVE-2013-7450 | High | 2017-04-03 | Not applicable | No public exploit | Pulp before 2.3.0 uses the same the same certificate authority key and certificate for all installations. |