dbcve.org
GobblinApplication · Apache

CVE-2021-36151

MEDIUM · 5.5 CVSS v3.1 Published 2022-02-04
Fix available
A fix is available. Upgrade to after 0.15.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Apache Gobblin, the Hadoop token is written to a temp file that is visible to all local users on Unix-like systems. This affects versions <= 0.15.0. Users should update to version 0.16.0 which addresses this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Apache Gobblin versions 0.15.0 and earlier, Hadoop authentication tokens are written to a temporary file with overly permissive file permissions, making them readable by all local users on Unix-like systems. This exposes sensitive credential information to local privilege escalation attacks.

MitigationUpgrade Apache Gobblin to version 0.16.0 or later to resolve the insecure temp file handling. Verify no legacy temp files containing tokens remain on systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GobblinApplication
Affected:<= 0.15.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Apache Gobblin is installed
    Search for Gobblin installation directories or check common deployment locations. Look for the 'gobblin' or 'gobblin-dist' package in your package manager or application deployment directory.
    Affected if Apache Gobblin is found on the system and the version is 0.15.0 or earlier.
  2. Determine the installed Gobblin version
    Check the version file or manifest within the Gobblin installation directory. Common locations include a VERSION file, build.properties, or the jar manifest. Run: find /path/to/gobblin -name 'VERSION' -o -name 'build.properties' 2>/dev/null and examine the contents.
    Affected if The version string shows 0.15.0 or any version lower than 0.15.0.
  3. Locate temporary files created by Gobblin
    Search temp directories (such as /tmp, /var/tmp, or the system temp directory configured in java.io.tmpdir) for files that may contain Hadoop authentication tokens. Look for files with patterns like 'token', 'hadoop', 'credentials', or files created by Gobblin processes. Use: find /tmp -type f -user <gobblin-user> -mtime -30 2>/dev/null to find recently created temp files.
    Affected if Temporary files containing Hadoop authentication tokens or credential data are found with overly permissive (world-readable) permissions.
  4. Verify file permissions on Gobblin temp files
    If temp files containing tokens are found, check their permissions using 'ls -la <file>'. Verify if other users on the system have read access (permissions ending in 'r--' or 'rw-r--r--' rather than restricted modes like '600' or '700').
    Affected if Any file containing Hadoop authentication tokens has permissions allowing read access by all users (e.g., mode 644, 655, or 777).

A system is affected if Apache Gobblin version 0.15.0 or earlier is installed and temporary files containing Hadoop authentication tokens exist with world-readable permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.15.0
Interim mitigation

Upgrade Apache Gobblin to version 0.16.0 or later to resolve the insecure temp file handling. Verify no legacy temp files containing tokens remain on systems.

Recommended fix High confidence

0.16.0

  1. Backup your current Gobblin installation and configuration
  2. Download Apache Gobblin version 0.16.0 from the official Apache distribution mirrors or repository
  3. Review the Gobblin 0.16.0 release notes for any configuration or behavior changes that may affect your deployment
  4. Test the upgrade in a non-production environment to ensure compatibility with your existing workflows and integrations
  5. Deploy version 0.16.0 to production after successful validation
Caveat Review 0.16.0 release notes for potential configuration or API changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gobblin Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-36151 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-36151 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data