dbcve.org
Debian LinuxOperating system · Debian

CVE-2018-10857

HIGH · 7.5 CVSS v3.0 Published 2018-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
git-annex is vulnerable to a private data exposure and exfiltration attack. It could expose the content of files located outside the git-annex repository, or content from a private web server on localhost or the LAN.

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 confidence

git-annex contains a path traversal and server-side request forgery (SSRF) vulnerability that allows unauthorized access to files outside the repository boundaries and enables exfiltration of content from private web servers on localhost or the local area network.

MitigationUpgrade git-annex to the patched version. Additionally, restrict git-annex process permissions and network access to minimize exposure until the patch can be applied.

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
Debian LinuxOperating system
Affected:= 8.0
Git AnnexApplication
Affected:all versions

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.0/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 checks

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

  1. Verify git-annex is installed
    Run `which git-annex` or check your package manager for the git-annex package
    Affected if git-annex is found on the system - all versions are vulnerable
  2. Check git-annex version
    Run `git-annex version` to obtain the exact version number
    Affected if Any version returned confirms git-annex is present and all versions are affected according to the CVE data
  3. Identify if webapp or web remote is enabled
    Check for running git-annex webapp processes with `ps aux | grep git-annex` and examine `.git/annex` configuration for web remote definitions
    Affected if The webapp feature or web remote is configured, as this is the likely attack vector for the SSRF and path traversal
  4. Check for exposed network listeners
    Run `netstat -tlnp | grep git-annex` or `ss -tlnp | grep git-annex` to see if git-annex is listening on network ports
    Affected if git-annex is listening on external network interfaces, enabling remote attackers to exploit the SSRF
  5. Review git-annex remote configurations
    Run `git-annex info` and examine `.git/annex/` directory for JSON configuration files describing remotes
    Affected if Web or HTTP remotes are configured that could be abused for path traversal or SSRF attacks

If git-annex is installed with the webapp or web remote feature enabled and exposed on the network, the environment is vulnerable to path traversal and SSRF exploitation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade git-annex to the patched version. Additionally, restrict git-annex process permissions and network access to minimize exposure until the patch can be applied.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-10857 — 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-2018-10857 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