CVE-2023-43612
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 · uneditedin OpenHarmony v3.2.2 and prior versions allow a local attacker arbitrary file read and write through improper preservation of permissions.
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 confidenceOpenHarmony v3.2.2 and prior versions contain a vulnerability where improper preservation of permissions during file operations allows a local attacker to read and write arbitrary files. The vulnerability stems from the OS failing to correctly handle or enforce permission checks when creating, accessing, or modifying files, enabling unauthorized file system access.
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.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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.
-
Determine OpenHarmony versionLocate the system version information for the OpenHarmony installation. This may be accessible via system settings, a 'version' or 'about' menu, or by querying the system properties using standard OS query commands.Affected if The installed version is OpenHarmony v3.2.2 or any prior version (anything <= 3.2.2).
-
Compare version against affected rangeVerify the exact version number obtained from the system against the affected range: OpenHarmony versions 3.2.2 and all prior versions.Affected if The version falls within the range of 3.2.2 or lower.
-
Confirm local file access exposureSince this vulnerability allows unauthorized file system access by a local attacker, test whether standard permission boundaries are enforced by creating files in restricted directories and observing if permission denials occur as expected.Affected if Files can be created or accessed outside the intended permission boundaries, indicating the permission handling flaw is present.
A user is affected if their OpenHarmony installation is version 3.2.2 or any prior version, as the flawed permission handling during file operations enables unauthorized file system access.
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 · scopedUpgrade OpenHarmony to a version beyond v3.2.2 that contains the patched permission handling logic, or apply vendor-supplied security patches for this issue.
OpenHarmony 3.2.3 or later
- Verify current OpenHarmony version by checking system settings or build configuration
- Backup all critical data and configurations
- Upgrade OpenHarmony to version 3.2.3 or later release which contains the security fix for improper permission preservation
- After upgrade, verify the system is functioning correctly and check that file permissions are properly enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43612 — 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-43612 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