CVE-2024-53490
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 · uneditedFavorites-web 1.3.0 favorites-web has a directory traversal vulnerability in SecurityFilter.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 confidenceFavorites-web version 1.3.0 contains a directory traversal vulnerability in SecurityFilter.java. This allows attackers to manipulate file path inputs using ".." sequences to access files and directories outside the web application's intended root folder.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 Favorites-web versionCheck the application manifest, pom.xml, build.gradle, or version file for the installed Favorites-web version. Common locations: META-INF/MANIFEST.MF, WEB-INF/classes, or the application's about/version endpoint.Affected if Installed version is 1.3.0 (the only version explicitly listed as affected)
-
Locate SecurityFilter.javaSearch the deployed web application for SecurityFilter.java in the source code or decompiled classes. Check the WEB-INF/classes or WEB-INF/lib directories for the compiled SecurityFilter class.Affected if SecurityFilter.java exists in the deployment (required for the vulnerability to be present)
-
Verify SecurityFilter handles file pathsInspect SecurityFilter.java source code or decompiled bytecode to confirm it processes file path inputs. Look for code that accepts, reads, or serves files based on user-supplied paths.Affected if SecurityFilter processes file path parameters without proper validation
-
Test for directory traversal vulnerabilitySend a test request with a path containing "../" sequences to endpoints handled by SecurityFilter (e.g., ?path=../../etc/passwd or similar file access parameters). Observe if the application returns files outside the intended root directory.Affected if The application returns files or directories when ".." sequences are used in path parameters, indicating the filter does not properly sanitize these sequences
If the installed version is 1.3.0 and SecurityFilter.java processes file path inputs, the application is vulnerable to directory traversal via ".." sequences.
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 input validation and path canonicalization in SecurityFilter.java to sanitize all file path inputs and restrict access to allowed directories only.
- 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-2024-53490 — 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-2024-53490 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