CVE-2024-28880
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 · uneditedPath traversal vulnerability in MosP kintai kanri V4.6.6 and earlier allows a remote attacker who can log in to the product to obtain sensitive information of the product.
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 · high confidenceA path traversal vulnerability in MosP kintai kanri V4.6.6 and earlier allows authenticated remote attackers to access files outside the intended directory by manipulating file path inputs, enabling disclosure of sensitive product information.
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
- 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 if MosP kintai kanri is installedSearch for MosP-related directories or web applications on the system. Common locations include application servers (Tomcat, etc.) or web root directories. Look for files or directories containing 'mosp' or 'kintai' in the name.Affected if MosP kintai kanri software is found on the system
-
Determine the installed versionCheck version information in the application typically found in: 1) Version files in the installation directory, 2) The application configuration files, 3) The application's main JAR file properties, 4) Any about/info page exposed by the web interface. Compare the version number to 4.6.6.Affected if Installed version is 4.6.6 or earlier
-
Verify web interface accessibilityCheck if the MosP application is exposed via HTTP/HTTPS. Identify the URL path used to access the application (commonly /mosp or /kintai). Confirm the application is reachable over the network.Affected if The web interface is accessible from the network and accepts file path parameters via HTTP requests
-
Confirm authentication is requiredReview the application's login mechanism and access controls. Verify whether unauthenticated users can reach endpoints that accept file path parameters. Attempt to access file-related functionality without credentials if testing in an authorized environment.Affected if The application accepts file path parameters without requiring authentication, or allows authenticated users to pass arbitrary paths to file operations
-
Check for sensitive file exposureIf the application is exposed and accepts file path inputs, test (in an authorized manner only) whether directory traversal sequences like ../ can be used to access files outside the web root. Inspect application logs for any path traversal attempts or access to sensitive directories.Affected if File path parameters can be manipulated to access files outside the intended directory (e.g., using ../ sequences)
The system is affected if MosP kintai kanri version 4.6.6 or earlier is installed and the web interface exposes file path parameters to authenticated users without proper sanitization.
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 sanitization for all file path parameters, ensuring paths are canonicalized and restricted to allowed directories. Apply principle of least privilege to file system access controls.
- 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-2024-28880 — 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-28880 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