CVE-2022-42149
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 · uneditedkkFileView 4.0 is vulnerable to Server-side request forgery (SSRF) via controller\OnlinePreviewController.java.
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 confidencekkFileView 4.0 contains a Server-side request forgery (SSRF) vulnerability in the OnlinePreviewController.java component. Attackers can exploit this to make the server perform arbitrary requests to internal or external resources, potentially accessing internal services, cloud metadata endpoints, or internal network infrastructure.
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= 4.0.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 installed kkFileView versionCheck the application's version manifest, pom.xml, or the startup banner. Common locations: version file in the installation directory, or query the application's /api/version endpoint if available.Affected if The installed version is exactly 4.0.0 (this is the only affected version listed)
-
Locate OnlinePreviewController componentInspect the application deployment for the OnlinePreviewController.java file or its compiled class. This controller handles the online preview functionality.Affected if The OnlinePreviewController is present in the deployed application build
-
Verify web endpoint exposureCheck if the application exposes a web endpoint mapped to OnlinePreviewController. Common paths include /api/onlinePreview or similar URL preview endpoints. Review the application's routing configuration or web.xml.Affected if An online preview endpoint is publicly accessible without authentication
-
Check for URL parameter handlingExamine the OnlinePreviewController code or configuration to determine if it accepts and processes URL parameters from user input (such as a 'url' or 'fileUrl' parameter).Affected if The controller accepts user-supplied URLs without strict validation
-
Review URL validation implementationInspect the code that processes URL parameters in OnlinePreviewController. Look for URL validation logic, allowlists, or deny lists for IP ranges and internal resources.Affected if No URL validation exists, or validation can be bypassed (e.g., no block on 127.0.0.0/8, 10.0.0.0/8, 192.168.0.0/16 ranges)
A user is affected if they are running kkFileView version 4.0.0 with the OnlinePreviewController endpoint exposed and accessible without proper URL validation safeguards in place.
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 dataImplement strict URL validation with allowlists in the OnlinePreviewController to restrict URLs to trusted domains, block requests to internal IP ranges (127.0.0.0/8, 10.0.0.0/8, 192.168.0.0/16, etc.), and validate all user-supplied URL parameters before making server-side requests.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42149 — 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-42149 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