CVE-2024-0935
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 · uneditedInsertion of Sensitive Information into Log File vulnerabilities are affecting DELMIA Apriso Release 2019 through Release 2024
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 · low confidenceDELMIA Apriso contains a vulnerability where sensitive information is being written to log files across Release 2019 through Release 2024. This could allow unauthorized users with access to the log files to obtain sensitive data that should not be exposed.
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>= 2019, <= 2024CVSS 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 DELMIA Apriso installed versionLocate the Apriso installation directory and check the version information, typically found in the application's About section, version manifest, or installation metadata filesAffected if The installed version is any release from 2019 through 2024 (inclusive)
-
Locate DELMIA Apriso log filesSearch the Apriso installation directory and application data folders for log files with extensions such as .log, typically found in logs subdirectories or alongside configuration filesAffected if Log files exist in the Apriso environment
-
Inspect log files for sensitive informationOpen recent log files and search for patterns indicating sensitive data: keywords like 'password', 'pwd', 'token', 'key', 'secret', 'credential', or look for base64-encoded strings and API keysAffected if Log files contain any plaintext or encoded sensitive credentials, authentication tokens, or private data that should not be exposed
-
Review logging configuration settingsExamine Apriso configuration files (commonly in config or settings folders) for logging-related settings that control what data gets written to logsAffected if Logging configuration permits or fails to filter sensitive parameters from being recorded
-
Check log file access controlsVerify file system permissions on log directories to determine if unauthorized users could read these filesAffected if Log files are readable by users who should not have access to potentially sensitive operational data
A user is affected if DELMIA Apriso version 2019-2024 is installed and log files contain sensitive information such as credentials, passwords, tokens, or other private data that should not be exposed.
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 dataReview and modify logging configurations to prevent sensitive information from being written to log files; implement proper log access controls and consider log sanitization or redaction solutions.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0935 — 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-0935 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