CVE-2023-6729
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 · uneditedNokia SR OS routers allow read-write access to the entire file system via SFTP or SCP for users configured with "access console." Consequently, a low privilege authenticated user with "access console" can read or replace the router configuration file as well as other files stored in the Compact Flash or SD card without using CLI commands. This type of attack can lead to a compromise or denial of service of the router after the system is rebooted.
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 confidenceNokia SR OS routers expose the entire file system via SFTP or SCP to users configured with 'access console,' allowing low-privilege authenticated users to read or replace router configuration files and other data stored on Compact Flash or SD cards without using CLI commands.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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.
-
Identify users with access console privilegeReview user account configurations on the router to list accounts that have the 'access console' privilege level configuredAffected if Any user account is configured with 'access console' privilege and SFTP/SCP access is enabled
-
Confirm SFTP or SCP service is activeCheck the router's configured services or daemon status to determine if SFTP or SCP server functionality is enabledAffected if SFTP or SCP service is running and accepting connections
-
Verify file system access via SFTP/SCPAttempt an SFTP or SCP login using a test account with 'access console' privilege and enumerate accessible directoriesAffected if The entire file system including Compact Flash and SD card directories are accessible via SFTP/SCP to low-privilege users
-
Check Compact Flash and SD card mountingInspect the router's storage configuration to confirm if Compact Flash or SD cards are mounted and accessible through the file systemAffected if Compact Flash or SD cards are present and exposed through the file system to authenticated users
-
Review user role file access controlsExamine the router's access control settings to determine if file system access is restricted by user role for SFTP/SCP sessionsAffected if No role-based restrictions limit which directories users with 'access console' can access via SFTP/SCP
The environment is affected if SFTP or SCP is enabled and users with 'access console' privilege can read or write to the entire file system including Compact Flash and SD cards without CLI-imposed restrictions.
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 dataRestrict or disable SFTP/SCP access for users with 'access console' privileges, implement proper file system access controls following least-privilege principles, and review user role configurations.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6729 — 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-6729 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