dbcve.org
NovajoinApplication · Python

CVE-2019-10138

HIGH · 8.8 CVSS v3.1 Published 2019-07-30
Fix available
A fix is available. Upgrade to 1.1.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A flaw was discovered in the python-novajoin plugin, all versions up to, excluding 1.1.1, for Red Hat OpenStack Platform. The novajoin API lacked sufficient access control, allowing any keystone authenticated user to generate FreeIPA tokens.

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

The python-novajoin plugin for Red Hat OpenStack Platform contains an access control flaw where the novajoin API lacks sufficient authorization checks. Any user authenticated through Keystone (the OpenStack identity service) can generate FreeIPA tokens, potentially allowing unauthorized access to the FreeIPA identity management system and its privileged operations.

MitigationUpdate python-novajoin to version 1.1.1 or later to obtain the patched version. After updating, verify that role-based access controls are properly enforced and that unauthenticated or unauthorized Keystone users can no longer generate FreeIPA tokens.

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
NovajoinApplication
Affected:< 1.1.1

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 the installed python-novajoin version
    Query the installed package version using the package manager (e.g., rpm -q python-novajoin or pip show python-novajoin) or check the version file in the novajoin installation directory
    Affected if The installed version is lower than 1.1.1 (e.g., 1.0.x, 1.1.0, or any version number below 1.1.1)
  2. Confirm novajoin API service is running
    Check if the novajoin API service process is active and listening on its configured port (typically via systemctl status novajoin-api or ps aux | grep novajoin)
    Affected if The novajoin API service is running and exposed to network traffic from Keystone-authenticated users
  3. Verify Keystone authentication is enabled
    Inspect the novajoin configuration file (usually /etc/novajoin/novajoin.conf or /etc/novajoin.conf) for the [keystone] section and confirm authentication is configured
    Affected if Keystone authentication is configured and any valid Keystone user can authenticate to novajoin without additional role checks
  4. Confirm FreeIPA integration is active
    Review the novajoin configuration for FreeIPA-related settings (such as freeipa_section or ipa_* parameters) and verify the service is connected to a FreeIPA server
    Affected if FreeIPA integration is configured and the novajoin service can communicate with a FreeIPA server for token generation
  5. Check for missing role-based access controls
    Review the novajoin API policy configuration (policy.json file) and the code handling token generation endpoints to verify if admin role enforcement exists
    Affected if No role restrictions are enforced on the token generation endpoint, allowing any authenticated Keystone user to request FreeIPA tokens

A system is affected if python-novajoin version is below 1.1.1 and the novajoin API is running with Keystone authentication and FreeIPA integration enabled, permitting any authenticated Keystone user to generate FreeIPA tokens without authorization checks.

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.

From vendor data
Upgrade available Upgrade to 1.1.1 or later
Fixed in 1.1.1
Interim mitigation

Update python-novajoin to version 1.1.1 or later to obtain the patched version. After updating, verify that role-based access controls are properly enforced and that unauthenticated or unauthorized Keystone users can no longer generate FreeIPA tokens.

Fix this in Novajoin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10138 — 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-2019-10138 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