CVE-2019-16919

Harbor API has a Broken Access Control vulnerability. The vulnerability allows project administrators to use the Harbor API to create a robot account with unauthorized push and/or pull access permissions to a project they dont have access or control for. The Harbor API did not enforce the proper project permissions and project scope on the API request to create a new robot account.

Weakness

During installation, installed file permissions are set to allow anyone to modify those files.

Affected Software

Potential Mitigations

• Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
• Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/1.html
• https://cwe.mitre.org/data/definitions/127.html
• https://cwe.mitre.org/data/definitions/81.html

References

• http://www.vmware.com/security/advisories/VMSA-2019-0016.html
• https://github.com/goharbor/harbor/security/advisories/GHSA-x2r2-w9c7-h624
• https://landscape.cncf.io/selected=harbor