References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to nvd@nist.gov.

Known Affected Software Configurations Switch to CPE 2.2

Change History

OR
     *cpe:2.3:a:datahub_project:datahub:*:*:*:*:*:*:*:* versions up to (excluding) 0.11.1

NIST AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

NIST CWE-327

https://github.com/datahub-project/datahub/security/advisories/GHSA-fg9x-wvqw-6gmw No Types Assigned

https://github.com/datahub-project/datahub/security/advisories/GHSA-fg9x-wvqw-6gmw Third Party Advisory

GitHub, Inc. AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L

GitHub, Inc. CWE-327

DataHub is an open-source metadata platform. The HMAC signature for DataHub Frontend sessions was being signed using a SHA-1 HMAC with the frontend secret key. SHA1 with a 10 byte key can be brute forced using sufficient resources (i.e. state level actors with large computational capabilities). DataHub Frontend was utilizing the Play LegacyCookiesModule with default settings which utilizes a SHA1 HMAC for signing. This is compounded by using a shorter key length than recommended by default for t

GitHub, Inc. https://github.com/datahub-project/datahub/security/advisories/GHSA-fg9x-wvqw-6gmw [No types assigned]