dbcve.org
Security Event ManagerApplication · Solarwinds

CVE-2022-38115

MEDIUM · 5.3 CVSS v3.1 Published 2022-11-23
Fix available
A fix is available. Upgrade to 2022.2 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
Insecure method vulnerability in which allowed HTTP methods are disclosed. E.g., OPTIONS, DELETE, TRACE, and PUT

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

This is an information disclosure vulnerability where the web server responds to HTTP requests by revealing which methods are allowed (OPTIONS, DELETE, TRACE, PUT, etc.). An attacker can send HTTP requests and analyze the Allow or Public header responses to discover enabled methods, which provides reconnaissance information for planning further attacks.

MitigationConfigure the web server to either restrict allowed HTTP methods to only those necessary (typically GET, POST, HEAD) or disable response headers that disclose allowed methods.

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
Security Event ManagerApplication
Affected:< 2022.2

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. Verify Solarwinds Security Event Manager is installed
    Locate the SEM web interface by accessing the hostname or IP where the product is hosted via a web browser
    Affected if The product web interface is accessible and responds to HTTP requests
  2. Determine the installed version
    Log into the SEM administrative interface and navigate to the About or System Information section to confirm the version number
    Affected if The installed version is below 2022.2 (for example, 2022.1.x or earlier)
  3. Send an OPTIONS request to the web server
    Use a tool like curl with the OPTIONS HTTP method: curl -X OPTIONS http://<hostname> -I or use a browser developer tool to send an OPTIONS request
    Affected if The response contains an Allow or Public header listing supported HTTP methods such as OPTIONS, DELETE, TRACE, PUT, or HEAD
  4. Test individual HTTP methods for unexpected responses
    Send requests using methods like TRACE, PUT, DELETE, PATCH to the web server endpoints using curl: curl -X TRACE http://<hostname>/
    Affected if The server responds with a successful response or reveals method support rather than rejecting the request with a 405 Method Not Allowed error

A system is affected if it is running Solarwinds Security Event Manager versions prior to 2022.2 AND the web server returns Allow or Public headers exposing enabled HTTP methods.

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 2022.2 or later
Fixed in 2022.2
Interim mitigation

Configure the web server to either restrict allowed HTTP methods to only those necessary (typically GET, POST, HEAD) or disable response headers that disclose allowed methods.

Recommended fix Moderate confidence

Security Event Manager 2022.2

  1. 1. Backup current Security Event Manager installation and configuration
  2. 2. Download Security Event Manager version 2022.2 or later from the SolarWinds customer portal
  3. 3. Stop the Security Event Manager service
  4. 4. Install the updated version (2022.2+) following standard upgrade procedures
  5. 5. Verify the installation completed successfully
  6. 6. Restart the Security Event Manager service
  7. 7. Confirm that the insecure HTTP methods (OPTIONS, DELETE, TRACE, PUT) are no longer exposed
Caveat Review release notes for any configuration changes or feature modifications between your current version and 2022.2

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

Fix this in Security Event Manager Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38115 — 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-38115 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