dbcve.org
FilrApplication · Microfocus

CVE-2022-38755

MEDIUM · 5.3 CVSS v3.1 Published 2022-11-21
Fix available
A fix is available. Upgrade to 4.3.1.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability has been identified in Micro Focus Filr in versions prior to 4.3.1.1. The vulnerability could be exploited to allow a remote unauthenticated attacker to enumerate valid users of the system. Remote unauthenticated user enumeration. This issue affects: Micro Focus Filr versions prior to 4.3.1.1.

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 confidence

Micro Focus Filr prior to version 4.3.1.1 contains a user enumeration vulnerability that allows remote unauthenticated attackers to determine valid usernames in the system. This is typically exploited by sending requests to authentication or user lookup endpoints and analyzing differences in responses (such as error messages, HTTP status codes, or response times) between valid and invalid usernames.

MitigationUpgrade Micro Focus Filr to version 4.3.1.1 or later to remediate this vulnerability.

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
FilrApplication
Affected:< 4.3.1.1

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Filr version
    Access the Filr administration console or check the product version via the /about endpoint typically found at /ssf/about or via the admin UI. Alternatively, check system documentation or the software inventory.
    Affected if The installed version is lower than 4.3.1.1
  2. Identify authentication endpoints
    Locate the login and user lookup endpoints exposed by Filr. Common paths include /ssf/login, /ssf/user/lookup, or similar REST API endpoints under the /ssf path.
    Affected if Authentication or user lookup endpoints are accessible without authentication
  3. Test for user enumeration via login endpoint
    Send HTTP POST requests to the login endpoint with known invalid usernames and compare the responses to requests with valid usernames. Look for differences in error messages, HTTP status codes, or response times.
    Affected if The system returns different error messages, status codes, or timing differences for valid versus invalid usernames
  4. Test for user enumeration via user lookup endpoint
    Send HTTP GET or POST requests to user lookup/search endpoints with various username inputs and analyze the responses for differences between existing and non-existing accounts.
    Affected if The system reveals whether a username exists through different error messages, response codes, or response content
  5. Check network exposure
    Verify if the Filr web interface is exposed to the internet or untrusted networks. Review firewall rules and access controls to determine if unauthenticated attackers can reach the authentication endpoints.
    Affected if The Filr authentication endpoints are reachable from untrusted networks without authentication

The environment is affected if the installed Filr version is below 4.3.1.1 AND the authentication/user lookup endpoints are accessible and exhibit different responses for valid versus invalid usernames.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.3.1.1 or later
Fixed in 4.3.1.1
Interim mitigation

Upgrade Micro Focus Filr to version 4.3.1.1 or later to remediate this vulnerability.

Recommended fix Moderate confidence

Filr 4.3.1.1 or later

  1. Verify current Filr version by accessing the Filr administrative interface or checking system documentation
  2. Schedule maintenance window for the upgrade process
  3. Back up the current Filr configuration and database according to Micro Focus backup procedures
  4. Download Filr version 4.3.1.1 or later from the Micro Focus software delivery platform
  5. Follow Micro Focus official upgrade documentation to apply the update
  6. After upgrade, verify the fix by attempting user enumeration to confirm the vulnerability is resolved
  7. Monitor system logs for any unusual authentication activity

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Filr Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38755 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38755 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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