CVE-2022-48476
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 JetBrains Ktor before 2.3.0 path traversal in the `resolveResource` method was possible
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 JetBrains Ktor before version 2.3.0 in the resolveResource method allows attackers to access files outside the intended resource directory by manipulating file paths with traversal sequences (e.g., '../'). This could enable unauthorized access to sensitive filesystem resources.
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< 2.3.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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 Ktor dependency in your projectCheck your build configuration file (build.gradle, build.gradle.kts, pom.xml) for the ktor-server-core or ktor-server dependencies and note the version numberAffected if The declared ktor version is below 2.3.0
-
Verify Ktor version in dependenciesRun './gradlew dependencies' (Gradle) or 'mvn dependency:tree' (Maven) and locate ktor-server-core or ktor-server artifacts to confirm the actual resolved versionAffected if The resolved ktor-server-core or ktor-server version is less than 2.3.0
-
Check for resolveResource usage in codeSearch your codebase for calls to resolveResource method: 'grep -r "resolveResource" --include="*.kt" .' or equivalent search in your IDEAffected if Your application code calls resolveResource and the Ktor version is below 2.3.0
-
Examine static content configurationInspect your application routing configuration where static resources are served, looking for routes using 'resources' or 'resolveResource' functionsAffected if Static resource serving is configured using resolveResource and the Ktor version is below 2.3.0
You are affected if your environment uses JetBrains Ktor with a version lower than 2.3.0 and your application serves static resources using the resolveResource method, which could allow path traversal attacks.
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 · scoped2.3.0
Upgrade JetBrains Ktor to version 2.3.0 or later to obtain the patch for this vulnerability. Review existing usages of resolveResource to ensure no exploitation has occurred.
2.3.0 or later
- Identify the build tool used in your project (Maven or Gradle)
- Locate the Ktor dependency declaration in your build configuration file (pom.xml or build.gradle/kts)
- Update the Ktor version to 2.3.0 or later
- Run your project's dependency update mechanism (e.g., ./gradlew dependencies or mvn dependency:tree) to verify the new version is resolved
- Rebuild and test your application to ensure the upgrade does not introduce regressions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.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,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-48476 — 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-48476 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