CVE-2022-2336
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 · uneditedSofting Secure Integration Server, edgeConnector, and edgeAggregator software ships with the default administrator credentials as `admin` and password as `admin`. This allows Softing to log in to the server directly to perform administrative functions. Upon installation or upon first login, the application does not ask the user to change the `admin` password. There is no warning or prompt to ask the user to change the default password, and to change the password, many steps are required.
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 · high confidenceSofting Secure Integration Server, edgeConnector, and edgeAggregator ship with a hardcoded default administrator account (admin/admin). The application does not prompt or require users to change this default password upon installation or first use, leaving the administrative interface accessible to anyone with knowledge of these default credentials.
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.1= 3.1= 5.2= 6= 1.22= 1.74CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify installed Softing productsCheck system for installed Softing software: look for Softing Edgeaggregator, Edgeconnector, Secure Integration Server, or Uagates in installed programs (Windows: Registry uninstall key, Linux: dpkg/rpm or /opt directory scan)Affected if Any of these products are installed at versions listed (Edgeaggregator, Edgeconnector = 3.1; Secure Integration Server = 1.22; Uagates = 1.74) or lower
-
Locate application configuration directorySearch for Softing application data folders: commonly in C:\ProgramData\Softing\ (Windows) or /var/opt/softing/ (Linux), or application installation directoryAffected if Configuration directories exist for any affected Softing product
-
Check for default credential persistenceExamine configuration files (XML, JSON, INI, or database files) in the application data directory for user account settings, password hashes, or authentication configurationAffected if Configuration files contain admin account settings with unchanged default password values or lack evidence of password modification (no password change timestamp, no password policy enforcement flag)
-
Verify password change enforcement statusLook for configuration flags or settings related to first-login password change, password expiration, or mandatory password resetAffected if No mandatory password change flag is set, or password change enforcement is disabled in the application configuration
If a Softing product from the affected list is installed and the admin account still uses the default password or has no enforced password change requirement, the environment is vulnerable to CVE-2022-2336.
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 change the default admin password to a strong, unique credential. Implement a mandatory password change on first login or installation, and simplify the password change process to reduce user burden.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2336 — 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-2022-2336 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