CVE-2023-32079
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 · uneditedNetmaker makes networks with WireGuard. A Mass assignment vulnerability was found in versions prior to 0.17.1 and 0.18.6 that allows a non-admin user to escalate privileges to those of an admin user. The issue is patched in 0.17.1 and fixed in 0.18.6. If Users are using 0.17.1, they should run `docker pull gravitl/netmaker:v0.17.1` and `docker-compose up -d`. This will switch them to the patched users If users are using v0.18.0-0.18.5, they should upgrade to v0.18.6 or later. As a workaround, someone using version 0.17.1 can pull the latest docker image of the backend and restart the server.
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 confidenceNetmaker versions prior to 0.17.1 and 0.18.6 contain a mass assignment vulnerability that allows authenticated non-admin users to modify restricted fields via API requests, enabling privilege escalation to administrator-level access. This authorization bypass stems from insufficient validation of user-supplied input during object creation or modification operations.
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< 0.17.1>= 0.18.0, <= 0.18.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine Netmaker versionRun 'docker ps' to find the container, then 'docker inspect <container_id>' or check the image tag in docker-compose.yml to identify the installed versionAffected if The version is < 0.17.1 or >= 0.18.0 and <= 0.18.5
-
Check API accessibilityVerify that the Netmaker API ports (443 or 8081 by default) are exposed externally or accessible to untrusted networksAffected if The API is reachable from untrusted networks without proper network segmentation
-
Identify non-admin usersQuery the Netmaker API or database to list user accounts and their rolesAffected if There are authenticated non-admin users in the system (these are the users who could exploit the mass assignment flaw)
You are affected if your Netmaker version is prior to 0.17.1 or between 0.18.0 and 0.18.5 inclusive, the API is accessible to authenticated users, and non-admin users exist in the system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.17.1
Upgrade Netmaker to version 0.17.1 (patched) or 0.18.6 or later (fixed) by pulling the updated Docker image and restarting the container with docker-compose.
Upgrade to Netmaker v0.18.6 or later (or v0.17.1 if on the 0.17.x line)
- For users on version 0.17.1: Run `docker pull gravitl/netmaker:v0.17.1` and then `docker-compose up -d` to apply the patched image
- For users on versions 0.18.0-0.18.5: Upgrade to version 0.18.6 or later by updating the docker image tag in your docker-compose.yml file and running `docker-compose up -d`
- After upgrading, verify the container is running the correct version using `docker ps` or checking the container logs with `docker logs <container_name>`
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-32079 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-32079 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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