CVE-2023-3512
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 · uneditedRelative path traversal vulnerability in Setelsa Security's ConacWin CB, in its 3.8.2.2 version and earlier, the exploitation of which could allow an attacker to perform an arbitrary download of files from the system via the "Download file" parameter.
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 a relative path traversal vulnerability in Setelsa Security's ConacWin CB (version 3.8.2.2 and earlier). The 'Download file' parameter does not properly sanitize user input, allowing attackers to use path traversal sequences (e.g., ../../../') to escape the intended directory and download arbitrary files from the host system.
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<= 3.8.2.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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if ConacWin CB is installedCheck for the ConacWin CB application on the system. This is typically a Windows-based application. Look for installation directories or check installed programs list.Affected if ConacWin CB is present on the system and the vulnerable 'Download file' feature is accessible to users.
-
Determine the installed versionLocate the version information for ConacWin CB. Check the application's About dialog, installation folder for version files, or examine the executable's properties (right-click the .exe file and view Details).Affected if The installed version is 3.8.2.2 or earlier.
-
Verify the 'Download file' feature is accessibleConfirm that the web interface or application provides a 'Download file' function that accepts user input. This is typically found in the application's file management or document retrieval module.Affected if The 'Download file' parameter is present and accepts user-supplied file paths.
-
Check for path traversal vulnerabilityIf you have access to test the application, attempt to use path traversal sequences in the 'Download file' parameter (e.g., ../../../windows/win.ini or similar) to see if arbitrary files can be accessed outside the intended directory.Affected if The application allows path traversal sequences and returns files from outside the intended directory.
You are affected if ConacWin CB version 3.8.2.2 or earlier is installed and the 'Download file' feature is accessible without proper path validation.
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 dataImplement strict input validation and path sanitization on the 'Download file' parameter, ensuring paths are restricted to an allowed base directory and reject any path containing traversal sequences.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3512 — 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-2023-3512 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