mirror of
https://github.com/cisagov/log4j-affected-db.git
synced 2024-10-31 22:28:26 +00:00
40 lines
1.2 KiB
YAML
40 lines
1.2 KiB
YAML
|
---
|
||
|
version: '1.0'
|
||
|
owners:
|
||
|
- name: cisagov
|
||
|
url: https://github.com/cisagov/log4j-affected-db
|
||
|
software:
|
||
|
- vendor: PagerDuty
|
||
|
product: PagerDuty SaaS
|
||
|
cves:
|
||
|
cve-2021-4104:
|
||
|
investigated: false
|
||
|
affected_versions: []
|
||
|
fixed_versions: []
|
||
|
unaffected_versions: []
|
||
|
cve-2021-44228:
|
||
|
investigated: false
|
||
|
affected_versions: []
|
||
|
fixed_versions: []
|
||
|
unaffected_versions: []
|
||
|
cve-2021-45046:
|
||
|
investigated: false
|
||
|
affected_versions: []
|
||
|
fixed_versions: []
|
||
|
unaffected_versions: []
|
||
|
cve-2021-45105:
|
||
|
investigated: false
|
||
|
affected_versions: []
|
||
|
fixed_versions: []
|
||
|
unaffected_versions: []
|
||
|
vendor_links:
|
||
|
- https://support.pagerduty.com/docs/pagerduty-log4j-zero-day-vulnerability
|
||
|
notes: We currently see no evidence of compromises on our platform. Our teams
|
||
|
continue to monitor for new developments and for impacts on sub-processors and
|
||
|
dependent systems. PagerDuty SaaS customers do not need to take any additional
|
||
|
action for their PagerDuty SaaS environment
|
||
|
references:
|
||
|
- ''
|
||
|
last_updated: '2021-12-21T00:00:00'
|
||
|
...
|