Overview 12 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 3 public PoC · 0 EPSS ≥ 0.5
12matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
3public PoC25.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
12
100.0%
Not applicable
0
0.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
12
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
3
25.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
9
75.0%
split by
peak 3 / quarter
Q4 181
Outside Waratek scope1
High1
not blocked1
Working exploit published1
Q1 193
Outside Waratek scope3
High1
Medium1
Low1
not blocked3
No public exploit3
Q2 193
Outside Waratek scope3
High2
Medium1
not blocked3
Working exploit published2
No public exploit1
Q3 190
Q4 190
Q1 201
Outside Waratek scope1
Medium1
not blocked1
No public exploit1
Q2 201
Outside Waratek scope1
Medium1
not blocked1
No public exploit1
Q3 200
Q4 200
Q1 210
Q2 211
Outside Waratek scope1
Medium1
not blocked1
No public exploit1
Q3 211
Outside Waratek scope1
Medium1
not blocked1
No public exploit1
Q4 210
Q1 220
Q2 220
Q3 221
Outside Waratek scope1
Critical1
not blocked1
No public exploit1
Q1 19Q3 19Q1 20Q3 20Q1 21Q3 21Q1 22Q3 22
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-2526 | Critical | 2022-09-09 | Outside Waratek scope | No public exploit | A use-after-free vulnerability was found in systemd. This issue occurs due to the on_stream_io() function and dns_stream_complete() function in 'resolved-dns-stream.c' not incrementing the reference counting for the DnsStream object. Therefore, other functions and callbacks called can dereference the DNSStream object, causing the use-after-free when the reference is still used later. |
| CVE-2021-33910 | Medium | 2021-07-20 | Outside Waratek scope | No public exploit | basic/unit-name.c in systemd prior to 246.15, 247.8, 248.5, and 249.1 has a Memory Allocation with an Excessive Size Value (involving strdupa and alloca for a pathname controlled by a local attacker) that results in an operating system crash. |
| CVE-2020-13529 | Medium | 2021-05-10 | Outside Waratek scope | No public exploit | An exploitable denial-of-service vulnerability exists in Systemd 245. A specially crafted DHCP FORCERENEW packet can cause a server running the DHCP client to be vulnerable to a DHCP ACK spoofing attack. An attacker can forge a pair of FORCERENEW and DCHP ACK packets to reconfigure the server. |
| CVE-2020-13776 | Medium | 2020-06-03 | Outside Waratek scope | No public exploit | systemd through v245 mishandles numerical usernames such as ones composed of decimal digits or 0x followed by hex digits, as demonstrated by use of root privileges when privileges of the 0x0 user account were intended. NOTE: this issue exists because of an incomplete fix for CVE-2017-1000082. |
| CVE-2019-20386 | Medium | 2020-01-21 | Outside Waratek scope | No public exploit | An issue was discovered in button_open in login/logind-button.c in systemd before 243. When executing the udevadm trigger command, a memory leak may occur. |
| CVE-2018-20839 | Medium | 2019-05-17 | Outside Waratek scope | No public exploit | systemd 242 changes the VT1 mode upon a logout, which allows attackers to read cleartext passwords in certain circumstances, such as watching a shutdown, or using Ctrl-Alt-F1 and Ctrl-Alt-F2. This occurs because the KDGKBMODE (aka current keyboard mode) check is mishandled. |
| CVE-2019-3844 | High | 2019-04-26 | Outside Waratek scope | Working exploit published | It was discovered that a systemd service that uses DynamicUser property can get new privileges through the execution of SUID binaries, which would allow to create binaries owned by the service transient group with the setgid bit set. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the GID will be recycled. |
| CVE-2019-3843 | High | 2019-04-26 | Outside Waratek scope | Working exploit published | It was discovered that a systemd service that uses DynamicUser property can create a SUID/SGID binary that would be allowed to run as the transient service UID/GID even after the service is terminated. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the UID/GID will be recycled. |
| CVE-2018-16888 | Medium | 2019-01-14 | Outside Waratek scope | No public exploit | It was discovered systemd does not correctly check the content of PIDFile files before using it to kill processes. When a service is run from an unprivileged user (e.g. User field set in the service file), a local attacker who is able to write to the PIDFile of the mentioned service may use this flaw to trick systemd into killing other services and/or privileged processes. Versions before v237 are vulnerable. |
| CVE-2018-16866 | Low | 2019-01-11 | Outside Waratek scope | No public exploit | An out of bounds read was discovered in systemd-journald in the way it parses log messages that terminate with a colon ':'. A local attacker can use this flaw to disclose process memory data. Versions from v221 to v239 are vulnerable. |
| CVE-2018-16865 | High | 2019-01-11 | Outside Waratek scope | No public exploit | An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when many entries are sent to the journal socket. A local attacker, or a remote one if systemd-journal-remote is used, may use this flaw to crash systemd-journald or execute code with journald privileges. Versions through v240 are vulnerable. |
| CVE-2018-15686 | High | 2018-10-26 | Outside Waratek scope | Working exploit published | A vulnerability in unit_deserialize of systemd allows an attacker to supply arbitrary state across systemd re-execution via NotifyAccess. This can be used to improperly influence systemd execution and possibly lead to root privilege escalation. Affected releases are systemd versions up to and including 239. |