CVE-2024-5650
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 · uneditedDLL Hijacking vulnerability has been found in CENTUM CAMS Log server provided by Yokogawa Electric Corporation. If an attacker is somehow able to intrude into a computer that installed affected product or access to a shared folder, by replacing the DLL file with a tampered one, it is possible to execute arbitrary programs with the authority of the SYSTEM account. The affected products and versions are as follows: CENTUM CS 3000 R3.08.10 to R3.09.50 CENTUM VP R4.01.00 to R4.03.00, R5.01.00 to R5.04.20, R6.01.00 to R6.11.10.
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 confidenceDLL hijacking vulnerability in Yokogawa CENTUM CAMS Log server allows an attacker with file system access to replace a legitimate DLL with a malicious one, achieving arbitrary code execution with SYSTEM-level privileges.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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.
-
Confirm Yokogawa CENTUM CAMS Log server is installedCheck for the product in Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or look for the installation directory (typically under C:\Program Files\Yokogawa\ or C:\Yokogawa\).Affected if The product is found on the system.
-
Identify the installed versionLocate the Log server executable (commonly named CAMSServer.exe, CAMSSrv.exe, or similar) and check its file properties for the version number, or query the Windows Registry for the installed version under the product's registry key.Affected if The version is lower than the patched version (contact Yokogawa for the specific fixed version number).
-
Locate the Log server installation directoryRight-click the executable and select 'Open file location' or use where.exe: where /R C:\ CAMSServer.exeAffected if The installation directory is found; this is where the vulnerable DLL would reside.
-
Identify replaceable DLLs in the installation folderList all DLL files in the Log server directory: dir /b *.dllAffected if Any DLL files are present in the installation directory that could be hijacked (attacker replaces a legitimate DLL with a malicious one).
-
Check if the Log server service runs with SYSTEM privilegesOpen Services, find the CENTUM CAMS Log server service, right-click and select Properties, or run: sc qc <service_name> to see the service account.Affected if The service runs as LocalSystem or a similarly privileged account (this enables SYSTEM-level code execution).
The environment is affected if Yokogawa CENTUM CAMS Log server is installed with vulnerable DLL files present and the service runs with elevated privileges.
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 dataReplace the vulnerable DLL with a secure version or apply vendor-provided patches; until a patch is available, restrict physical and network access to the installation directory and monitor for unauthorized DLL modifications.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5650 — 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-2024-5650 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