signing and validation − Identity integration and role-based access control − Security and vulnerability analysis − Image replication between instances − Internationalization (currently English and Architecture 13 13 API Routing Core Service (API/Auth/GUI) Image Registry Trusted Content Vulnerability Scanning Job Service Admin Service Harbor components 3rd party components SQL Database Key/Value Image is pulled using digest • Perform vulnerability scanning – Prevent images with vulnerabilities from being pulled – Regular scanning based on updated vulnerability database 23 Content trust for image

– RBAC: admin, developer, guest – AD/LDAP integration • Policy based image replication • Vulnerability Scanning • Notary • Web UI • Audit and logs • Restful API for integration • Lightweight and Replication Job Services Notary client Remote Harbor Instance Notary Registry V2 Vulnerability Scanning Admin Service Harbor users and partners (selected) 12 Image replication (synchronization) Image is pulled using digest • Perform vulnerability scanning – Prevent images with vulnerabilities from being pulled – Regular scanning based on updated vulnerability database 21 Content trust for image

summarised 6 fuzzers written and added to Istio's OSS-Fuzz integration 1 CVE found in Golang 1 vulnerability found that affected Googles managed Istio offering 11 issues found ● 5 system resource exhaustion affected Googleʼs managed Istio offering, and it led to further investigation that revealed a vulnerability in Golang itself. The finding was reported by the auditing team to the Istio maintainers, because connection, which could lead to a denial of service scenario if a large request was sent. This is a vulnerability, however, to be vulnerable, users would need the MultiplexHTTP option configured - used by some

the same Dapr building blocks. None of the issues were of critical or high severity. We found a vulnerability in a 3rd-party dependency which was assigned a CVE1 of high severity, however it did not impact is not enabled by default. The vulnerability had the potential to crash a Dapr sidecar with an out-of-memory denial of service attack vector. We found the vulnerability a�er performing the threat modelling example, if Dapr sends a request to a NodeJS application that triggers a remote code execution vulnerability in the NodeJS 10 Dapr security audit 2023 application3, this is entirely the responsibility

Harbor���� 6 x x Agenda 7 Confidential � ©2018 VMware, Inc. • Isolation • Access Control • Vulnerability • Content Trust • Replication • Control Policy SECURITY DISTRIBUTION RELIABILITY DEPLOYMENT ������������� Harbor�� API Routing Core Service (API/Auth/GUI) Image Registry Trusted Content Vulnerability Scanning Job Service Admin Service Harbor components 3rd party components SQL Database 12 Confidential � ©2018 VMware, Inc. SECURITY Isolation Access control Content Trust Vulnerability Scanning ���� NS �� ���� �� • ���������NS • ��������� • ������� • �������� ���� ����

Harbor���� 6 x x Agenda 7 Confidential � ©2018 VMware, Inc. • Isolation • Access Control • Vulnerability • Content Trust • Replication • Control Policy SECURITY DISTRIBUTION RELIABILITY DEPLOYMENT ������������� Harbor�� API Routing Core Service (API/Auth/GUI) Image Registry Trusted Content Vulnerability Scanning Job Service Admin Service Harbor components 3rd party components SQL Database 12 Confidential � ©2018 VMware, Inc. SECURITY Isolation Access control Content Trust Vulnerability Scanning ���� NS �� ���� �� • ���������NS • ��������� • ������� • �������� ���� ����

over the WP1-3 scope items and spotted only one new finding classified as a security vulnerability. This problem, however, was given a High score in terms of risk because it enables an access severity rank is simply given in brackets following the title heading for each vulnerability. Each vulnerability is additionally given a unique identifier (e.g. DAP-02-001) for the purpose of facilitating Pollution through invocation (Low) Status: Open During a review of the previously reported vulnerability, it was noticed that the HTTP Parameter Pollution is still possible, as demonstrated via the Proof-of-Concept

severity rank is simply given in brackets following the title heading for each vulnerability. Each vulnerability is additionally given a unique identifier (e.g. DAP-01-001) for the purpose of facilitating invocation (Low) It was found that the HTTP API of Dapr is vulnerable to a HTTP Parameter Pollution vulnerability when a service is locally or remotely invoked. The method parameter is received from the path vulnerable code snippets that did not provide an easy way to be called. Conclusively, while a vulnerability is present, an exploit might not always be possible. DAP-01-001 WP1: Sidecar allows MDNS probes

audit Distribution Policy • Based on content trust • Based on vulnerability • Based on RBAC Main Features （ Cont. ） 7 Vulnerability Scanning • Kinds of scanning policies • Elaborate scanning report Architecture API Routing API Routing Core Service (API/Auth/GUI) Image Registry Trusted Content Vulnerability Scanning Job Service Admin Service Harbor components 3rd party components SQL Database

CVE-2021-29063 - Mpmath v1.0.0 through v1.2.1 exposes a Regular Expression Denial of Service (ReDOS) vulnerability. ‣ Known security vulnerabilities: ‣ CVE-2022-32212, CVE-2022-43548, CVE-2023-0286, CVE-2022-32223 CVE-2021-29063 - Mpmath v1.0.0 through v1.2.1 exposes a Regular Expression Denial of Service (ReDOS) vulnerability. ‣ Known security vulnerabilities: ‣ CVE-2022-25882 for ONNX<1.13.0 PyTorch RN-08516-001_v23 CVE-2021-29063 - Mpmath v1.0.0 through v1.2.1 exposes a Regular Expression Denial of Service (ReDOS) vulnerability. PyTorch RN-08516-001_v23.07 | 69 Chapter 12. PyTorch Release 22.11 The NVIDIA container