CVE-2022-23553
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 · uneditedAlpine is a scaffolding library in Java. Alpine prior to version 1.10.4 allows URL access filter bypass. This issue has been fixed in version 1.10.4. There are no known workarounds.
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 confidenceAlpine is a Java scaffolding library. Versions prior to 1.10.4 contain a URL access filter bypass vulnerability, allowing attackers to access URLs that should be restricted by the filter mechanism. This could enable unauthorized access to protected 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< 1.10.4CVSS 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.
-
Locate Alpine library in your projectSearch for Alpine JAR files (alpine-*.jar) in your project's lib folder, dependencies (Maven pom.xml, Gradle build.gradle), or application runtime classpath. Also check for imports of 'org.alpine.*' packages in your source code.Affected if Alpine library is present in the project dependencies or classpath
-
Determine installed Alpine versionFor Maven projects: examine the <version> tag in pom.xml for 'alpine' dependency. For Gradle: check the version in build.gradle. For deployed applications: examine the JAR filename (e.g., alpine-1.10.3.jar) or inspect the manifest file inside the JAR.Affected if The version is lower than 1.10.4 (e.g., 1.10.3, 1.10.2, 1.10.1, etc.)
-
Verify URL access filter is in useSearch source code for Filter classes that extend or implement Alpine's filtering mechanism. Look for usage of classes like 'UrlAccessFilter' or configuration files that define URL access rules. Check if the application configures protected URL paths.Affected if The application uses Alpine's URL filter mechanism to restrict access to certain URLs
-
Confirm bypass condition is exploitableReview the application's filter configuration to identify protected endpoints. Test whether the filter can be bypassed using encoded URLs, path traversal sequences, or other bypass techniques described in the vulnerability disclosure.Affected if Protected URLs can be accessed without proper authorization through filter bypass
You are affected if your project uses Alpine library version lower than 1.10.4 AND utilizes Alpine's URL access filter to protect resources.
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 · scoped1.10.4
Upgrade Alpine to version 1.10.4 or later. No workarounds are available.
1.10.4
- Identify the Alpine dependency in your project's build configuration (pom.xml for Maven or build.gradle for Gradle)
- Locate the Alpine library dependency declaration
- Update the version attribute to 1.10.4
- Run the build to download the fixed version (e.g., mvn clean install for Maven or ./gradlew build for Gradle)
- Verify the updated version is correctly resolved in your dependency tree (e.g., mvn dependency:tree or ./gradlew dependencies)
- Rebuild and test your application to ensure the upgrade does not introduce issues
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23553 — 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-23553 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