CVE-2023-3350
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 · uneditedA Cryptographic Issue vulnerability has been found on IBERMATICA RPS, affecting version 2019. By firstly downloading the log file, an attacker could retrieve the SQL query sent to the application in plaint text. This log file contains the password hashes coded with AES-CBC-128 bits algorithm, which can be decrypted with a .NET function, obtaining the username's password in plain text.
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 confidenceThe vulnerability allows an attacker to download application log files through what appears to be an unauthenticated or improperly authorized file download mechanism. The log files contain SQL queries in plain text and password hashes encrypted with AES-CBC-128. The encryption key can be recovered from the application's .NET code, allowing decryption of the password hashes to plaintext.
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= 2019CVSS 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 Ayesa Ibermatica Rps installationCheck for the presence of the Ayesa Ibermatica Rps application directory or registry entries. Verify the installed version is 2019.Affected if The application is Ayesa Ibermatica Rps version 2019.
-
Locate the file download endpointInspect the application web configuration or source code for endpoints that serve log files. Look for handlers or routes that accept file parameters (e.g., ?file=logs/...).Affected if A download endpoint exists that allows unauthenticated access to arbitrary files.
-
Test for unauthenticated log file accessAttempt to access common log file paths via HTTP/HTTPS or the identified download endpoint without providing credentials.Affected if Log files are downloadable without authentication.
-
Inspect .NET code for AES keyDecompile or inspect the application's .NET binaries (DLL/EXE files) to locate hardcoded AES-CBC-128 encryption keys in the source code.Affected if The AES encryption key is hardcoded in the .NET application code.
-
Check log file contentsDownload any accessible log files and search for SQL query patterns and encrypted password hash strings.Affected if Log files contain SQL queries in plain text or encrypted password hashes.
You are affected if you run Ayesa Ibermatica Rps version 2019 and the application's log files are accessible without authentication, exposing SQL queries and AES-encrypted password hashes with a recoverable key.
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 dataImmediately restrict unauthorized access to log files and audit for compromised credentials. Replace encryption-based password storage with salted cryptographic hash functions (e.g., bcrypt, scrypt) and audit the key management implementation for the AES encryption.
- 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-3350 — 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-3350 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