LiveActive security incident?Get immediate response
CVE Record

CVE-2023-46186: IBM Jazz for Service Management information disclosure

IBM Jazz for Service Management 1.1.3.20 could allow an unauthorized user to obtain sensitive file information using forced browsing due to improper access controls. IBM X-Force ID: 269929.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

IBM Jazz for Service Management 1.1.3.20 has an access-control weakness that could let an unauthenticated user learn sensitive file information through forced browsing. The business risk is mainly confidentiality loss, not system takeover, data modification, or outage based on the provided CVSS data.

Executive priority

Treat as a moderate confidentiality risk. Prioritize confirmation if IBM Jazz for Service Management is internet-facing or handles sensitive operational data. If the product is not deployed, no action is indicated beyond documenting non-exposure.

Technical view

CVE-2023-46186 is CWE-425 forced browsing in IBM Jazz for Service Management 1.1.3.20. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, meaning remote unauthenticated access with low complexity and limited confidentiality impact. The source bundle does not name a fixed version or specific mitigation.

Likely exposure

Exposure is limited to organizations running IBM Jazz for Service Management 1.1.3.20, especially if the service is reachable from untrusted networks. The provided affected data marks other versions as unaffected by default, but asset inventory should verify exact deployed versions.

Exploitation context

The CVE is not listed as CISA KEV in the source bundle, and no cited source here states active exploitation. The issue is plausible to exploit remotely because it requires no privileges or user interaction, but the documented impact is limited information disclosure.

Researcher notes

The provided evidence supports product, version, weakness class, and CVSS characteristics. It does not provide exploit details, observed exploitation, vulnerable paths, fixed versions, or concrete configuration mitigations. Validation should stay inventory- and log-focused unless vendor guidance supplies authorized testing detail.

Mitigation direction

  • Check IBM advisory and X-Force entry for current fixed levels or interim guidance.
  • Identify and prioritize any IBM Jazz for Service Management 1.1.3.20 deployments.
  • Restrict service access to trusted networks and administrative users where possible.
  • Review application access controls around sensitive file resources.
  • Monitor for unusual requests targeting protected file information.

Validation and detection

  • Inventory deployed IBM Jazz for Service Management versions across all environments.
  • Confirm whether version 1.1.3.20 is present and reachable from untrusted networks.
  • Review vendor guidance before applying updates or configuration changes.
  • Check logs for suspicious forced-browsing patterns without attempting exploitation.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-425: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-46186 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2023-46186Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMJazz for Service Management1.1.3.20unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-425 · source CWE mapping

Direct Request ('Forced Browsing')

Direct Request ('Forced Browsing') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.