CVE-2022-46660
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 · uneditedAn unauthorized user could alter or write files with full control over the path and content of the file.
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 confidenceThis is an arbitrary file write vulnerability where an unauthenticated or unauthorized attacker can create or modify files on the server with full control over both the file path and its contents. This could allow code execution if writable paths include web-accessible directories, or configuration tampering, privilege escalation, and denial of service.
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>= 7.0, < 2023CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 installed Ge Proficy Historian versionCheck the installed version through Windows Registry under HKLM\SOFTWARE\GE Digital\Proficy Historian, or look in Add/Remove Programs, or query the Historian service information. Compare the major version to the affected range (7.0 through 2022).Affected if The installed version is 7.0 or higher but lower than 2023
-
Verify Historian server is accessibleConfirm the Historian server is running and network-accessible. Check if the ports used by Historian (typically 5450, 5432, or as configured) are listening and reachable.Affected if The Historian server is running and accepting connections - this is where the unauthenticated file write can be exploited
-
Confirm no external authentication proxy or firewallReview network architecture to determine if external access to Historian passes through an authentication layer or is blocked by firewall rules.Affected if External or unauthenticated users can directly reach the Historian service without authentication enforcement
You are affected if Ge Proficy Historian version 7.0 through 2022 is installed and the service is network-accessible without enforced authentication.
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 · scoped2023
Implement proper authentication and authorization checks before any file write operations, validate and sanitize all user-provided file paths to prevent directory traversal, and apply principle of least privilege to file system permissions.
2023
- Upgrade Proficy Historian to version 2023 or later to resolve the unrestricted file upload vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46660 — 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-2022-46660 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