CVE-2012-4959
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 · uneditedDirectory traversal vulnerability in NFRAgent.exe in Novell File Reporter 1.0.2 allows remote attackers to upload and execute files via a 130 /FSF/CMD request with a .. (dot dot) in a FILE element of an FSFUI record.
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 confidenceDirectory traversal vulnerability in NFRAgent.exe in Novell File Reporter 1.0.2 allows remote attackers to upload and execute arbitrary files by using '..' sequences in the FILE element of FSFUI records within 130/FSF/CMD requests, enabling traversal outside the intended directory and remote code execution.
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= 1.0.2CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Check if Novell File Reporter is installedLook for NFRAgent.exe in the installation directory, typically under C:\Program Files\Novell\File Reporter or C:\Program Files (x86)\Novell\File Reporter. Also check Windows Services for a service named 'NFRAgent' or similar.Affected if NFRAgent.exe exists on the system and the NFRAgent service is present
-
Verify the installed version is 1.0.2Right-click on NFRAgent.exe, select Properties, then view the Details tab to see the File Version. Alternatively, check the installed programs list in Windows Control Panel for 'Novell File Reporter' version 1.0.2.Affected if The installed version is exactly 1.0.2
-
Confirm the NFRAgent service is runningOpen Services (services.msc), locate the Novell File Reporter Agent service, and verify its Status is 'Running'. Also check if the service is set to start automatically.Affected if The NFRAgent service is actively running on the system
-
Check network exposure of the NFRAgent serviceRun 'netstat -an' or use a network port scanner to identify listening ports associated with NFRAgent.exe. The service typically listens on port 3037 or similar for 130/FSF/CMD requests.Affected if The NFRAgent service is listening on a network-accessible port and accepts remote connections
The system is affected if Novell File Reporter version 1.0.2 is installed with the NFRAgent service running and exposed to network requests.
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 dataApply vendor patch if available; otherwise restrict network access to the NFRAgent service and implement strict input validation on file path parameters to block traversal sequences.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2012-4959 — 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-2012-4959 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