Nginx Instance ManagerWeb server / proxy · F5
CVE-2022-35241
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 · uneditedIn versions 2.x before 2.3.1 and all versions of 1.x, when NGINX Instance Manager is in use, undisclosed requests can cause an increase in disk resource utilization. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
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 · moderate confidenceIn NGINX Instance Manager 2.x before 2.3.1 and all 1.x versions, certain undisclosed requests can trigger excessive disk resource utilization, likely through uncontrolled logging, temporary file creation, or similar disk-write 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
Nginx Instance ManagerWeb server / proxy
>= 1.0.0, <= 1.0.4>= 2.0.0, < 2.3.1CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Identify installed NGINX Instance Manager versionRun the command 'nginx-instance-manager version' or check via the API at /api/v1/version, or inspect the RPM/DEB package with 'rpm -q nginx-instance-manager' or 'dpkg -l nginx-instance-manager'Affected if Version is 1.0.0 through 1.0.4, or 2.0.0 through 2.3.0
-
Confirm version is within vulnerable rangeCompare the installed version number to the affected ranges: 1.0.0 <= version <= 1.0.4 OR 2.0.0 <= version < 2.3.1Affected if Installed version matches either of these ranges
-
Monitor disk usage for anomaliesCheck disk usage on the partition hosting NGINX Instance Manager with 'df -h' and review for unusual consumption, particularly in log directoriesAffected if Disk usage is unexpectedly high or growing rapidly without normal cause
-
Inspect log file growthExamine log directory (typically /var/log/nginx-instance-manager/) for abnormally large log files or rapid log growth using 'ls -lh' and 'du -sh *'Affected if Logs are excessively large or growing beyond normal operational patterns
A user is affected if their installed NGINX Instance Manager version falls within 1.0.0-1.0.4 or 2.0.0-2.3.0 AND they observe unexplained excessive disk utilization.
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.
From vendor data2.3.1
Upgrade NGINX Instance Manager to version 2.3.1 or later. For 1.x branches, consider migration to a supported 2.x version as 1.x is end-of-life.
Fix this in Nginx Instance Manager
Scoped from the published advisory
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35241 — 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-2022-35241 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