Uber Kraken through 0.1.29 Path Traversal via tag parameter
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.7epss 0.5%
exploitation probability
0.5%top 58% of all CVEs
observed exploitation
nono source reports it
Uber Kraken through 0.1.29 fails to validate the tag parameter in the /tags/{tag} endpoint, allowing unauthenticated attackers to traverse outside the configured storage root. Attackers can use percent-encoded parent-directory segments in the tag parameter to read arbitrary files accessible to the testfs backend process.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Affected products
uber · krakenReferences
https://github.com/uber/krakenhttps://github.com/uber/kraken/blob/v0.1.27/build-index/tagserver/server.go#L128-L129https://github.com/uber/kraken/blob/v0.1.27/lib/backend/namepath/pather.go#L78-L84https://github.com/uber/kraken/blob/v0.1.27/lib/backend/testfs/server.go#L165-L173https://github.com/uber/kraken/issues/645https://www.vulncheck.com/advisories/uber-kraken-through-0.1.29-path-traversal-via-tag-parameter