CVE-2022-30621
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 · uneditedAllows a remote user to read files on the camera's OS "GetFileContent.cgi". Reading arbitrary files on the camera's OS as root user.
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 confidenceA path traversal vulnerability in GetFileContent.cgi on IP cameras allows remote unauthenticated users to read arbitrary files from the filesystem with root privileges by manipulating file path parameters.
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= 3.2.0= 3.2.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the camera's web interface or check the device label/management console for the model name. Look for 'Cellinx Nvt Ip Ptz Camera' or similar Cellinx branding.Affected if The device is a Cellinx Nvt IP PTZ Camera
-
Check the firmware versionNavigate to the camera's web interface settings page (typically under System, Maintenance, or About) to view the firmware version. Alternatively, access the camera's API or management interface to query the firmware version.Affected if The firmware version is 3.2.0 or 3.2.1
-
Verify GetFileContent.cgi is accessibleAttempt to access the CGI script via HTTP/HTTPS at a path similar to /cgi-bin/GetFileContent.cgi or /cgi/GetFileContent.cgi on the camera's IP address.Affected if The GetFileContent.cgi endpoint responds to requests (returns any HTTP status other than 404 or connection refused)
-
Test for path traversal vulnerabilitySend a request to GetFileContent.cgi with a manipulated 'file' or 'path' parameter containing traversal sequences such as '../../../etc/passwd' or '../../../etc/shadow'. Monitor the response for file contents.Affected if The request returns the contents of files outside the expected directory, confirming the path traversal is exploitable
The environment is affected if the device is a Cellinx Nvt IP PTZ Camera running firmware version 3.2.0 or 3.2.1, and the GetFileContent.cgi endpoint is accessible and accepts path traversal sequences in file parameters.
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 dataRestrict network access to the affected camera, apply vendor patches if available, and implement input validation to prevent directory traversal in file read requests.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30621 — 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-30621 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