dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-1142

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Path Traversal in Sonatype IQ Server from version 143 allows remote authenticated attackers to overwrite or delete files via a specially crafted request. Version 171 fixes this issue.

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 confidence

Path traversal vulnerability in Sonatype IQ Server version 143 allows authenticated remote attackers to manipulate file paths in requests to overwrite or delete files outside the intended directory. The vulnerability stems from insufficient validation of user-supplied file path inputs, enabling directory traversal sequences (e.g., ../../) to access restricted filesystem locations.

MitigationUpgrade Sonatype IQ Server to version 171 or later, which contains the fix for this path traversal vulnerability. Additionally, restrict IQ Server access to only trusted authenticated users and implement network segmentation to limit exposure.

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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Sonatype IQ Server installation
    Search for IQ Server directories or check common installation paths such as /opt/sonatype/iq, /var/iq, or the directory where the application jar/war files are stored. Look for the file named 'nexus-iq-server' or similar.
    Affected if IQ Server is found on the system
  2. Identify installed IQ Server version
    Check the version file or banner displayed when starting the server. Common locations: examine the jar filename, check a version file in the installation directory, or query the server's API endpoint /api/v2/version if accessible.
    Affected if The installed version is 143 or any version lower than 171
  3. Verify authentication is enabled
    Examine the IQ Server configuration file (typically application.yml or config.yml in the conf directory) and confirm that authentication mechanisms are configured. Check for realm, security, or authentication-related settings.
    Affected if Authentication is disabled or uses weak/default credentials, making unauthorized access possible
  4. Confirm network exposure of IQ Server
    Check network listener configuration and firewall rules. Determine if the IQ Server web interface (port 8070 or 8443 by default) is accessible from untrusted networks.
    Affected if The IQ Server admin interface is exposed to untrusted networks or the internet
  5. Review file operation logs
    Examine IQ Server application logs for any suspicious file access requests containing ../ sequences or unusual file write/delete operations targeting locations outside the server's intended directories.
    Affected if Log entries show directory traversal attempts or unexpected file manipulations

A user is affected if their Sonatype IQ Server is version 143 or any version below 171 and the server is accessible to authenticated users who could exploit the path traversal flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Sonatype IQ Server to version 171 or later, which contains the fix for this path traversal vulnerability. Additionally, restrict IQ Server access to only trusted authenticated users and implement network segmentation to limit exposure.

Recommended fix High confidence

Sonatype IQ Server version 171

  1. Upgrade Sonatype IQ Server to version 171 or later to resolve the path traversal vulnerability.
  2. After upgrade, verify the IQ Server is running correctly and all services are operational.
  3. Review IQ Server logs to confirm no errors related to file operations after the upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1142 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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