CVE-2014-6287
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 · uneditedThe findMacroMarker function in parserLib.pas in Rejetto HTTP File Server (aks HFS or HttpFileServer) 2.3x before 2.3c allows remote attackers to execute arbitrary programs via a %00 sequence in a search action.
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 confidenceRejetto HTTP File Server (HFS) versions 2.3x before 2.3c contains a remote code execution vulnerability in the findMacroMarker function in parserLib.pas. The vulnerability allows remote attackers to execute arbitrary programs by sending a specially crafted request containing a %00 (null byte) sequence in a search action, bypassing input validation in the macro marker parsing logic.
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>= 2.3, < 2.3cCVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 HFS versionCheck the HFS application window title, or right-click the hfs.exe file, select Properties, and view the Version tab to find the product versionAffected if Version shows 2.3, 2.3a, 2.3b, or any 2.3x version prior to 2.3c
-
Compare version to vulnerable rangeCompare your installed HFS version against the affected range: 2.3 through 2.3b (any version >= 2.3 but < 2.3c)Affected if Installed version is 2.3, 2.3a, 2.3b, or equivalent 2.3x releases below 2.3c
-
Confirm HFS is runningOpen Task Manager and look for hfs.exe in the Processes tab, or run 'netstat -an | findstr :80' to check if port 80 is listeningAffected if HFS process is active and the HTTP service is listening on a network port
-
Verify search functionality is accessibleAttempt to reach the HFS search page by navigating to http://[your-server]/~search or checking if the search macro is enabled in HFS settingsAffected if The search feature is exposed without authentication restrictions
Your environment is vulnerable if HFS version is 2.3, 2.3a, or 2.3b and the search functionality is accessible over the network.
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 · scoped2.3c
Upgrade to HFS version 2.3c or later to obtain the patch. If immediate patching is not feasible, restrict or disable external network access to the HFS service until the update can be applied.
HFS version 2.3c or later
- 1. Back up your current HFS installation directory and configuration files.
- 2. Download Http File Server version 2.3c (or latest stable version) from the official Rejetto repository or trusted source.
- 3. Stop the currently running HFS service.
- 4. Replace the existing HFS executable and required files with the new version.
- 5. Restart the HFS service.
- 6. Verify the server is operational and test that the vulnerability is no longer exploitable.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6287 — 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-2014-6287 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