CVE-2022-0757
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 · uneditedRapid7 Nexpose versions 6.6.93 and earlier are susceptible to an SQL Injection vulnerability, whereby valid search operators are not defined. This lack of validation can allow a logged-in, authenticated attacker to manipulate the "ANY" and "OR" operators in the SearchCriteria and inject SQL code. This issue was fixed in Rapid7 Nexpose version 6.6.129.
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 confidenceRapid7 Nexpose versions 6.6.93 and earlier fail to define valid search operators, allowing authenticated attackers to manipulate the ANY and OR operators in SearchCriteria to inject arbitrary SQL code. This occurs due to insufficient input validation on search operator fields.
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<= 6.6.93CVSS 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.
-
Identify the installed Nexpose versionLog into the Nexpose web UI and navigate to Administration > System > General Information to view the product version. Alternatively, check the version file in the installation directory if you have server access.Affected if The version displayed is 6.6.93 or any version lower than 6.6.93
-
Verify Nexpose service is running and accessibleConfirm the Nexpose service is running and the web interface responds to requests. Attempt to access the login page with valid credentials.Affected if The service is running and accessible to authenticated users
-
Confirm user access to search functionalityCheck if any user roles include permission to use the search feature, particularly custom or saved searches using SearchCriteria with ANY or OR operators.Affected if Any authenticated user has access to the search feature
The environment is affected if the installed Nexpose version is 6.6.93 or earlier AND the search functionality is accessible to authenticated users.
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 · scopedUpgrade Rapid7 Nexpose to version 6.6.129 or later, which implements proper validation of search operators to prevent SQL injection.
6.6.129
- 1. Identify the current installed version of Rapid7 Nexpose by checking the application or using the version command
- 2. Download Rapid7 Nexpose version 6.6.129 or later from the official Rapid7 download portal
- 3. Back up the current Nexpose configuration and database according to Rapid7 backup procedures
- 4. Stop the Nexpose service before applying the upgrade
- 5. Install version 6.6.129 or later following the standard Nexpose upgrade documentation
- 6. Verify the upgrade was successful by checking the new version number
- 7. Restart the Nexpose service
- 8. Validate that the search functionality works correctly with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0757 — 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-0757 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