dbcve.org
Messaging GatewayApplication · Symantec

CVE-2022-25629

MEDIUM · 5.4 CVSS v3.1 Published 2022-12-09
Fix available
A fix is available. Upgrade to 10.8 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
An authenticated user who has the privilege to add/edit annotations on the Content tab, can craft a malicious annotation that can be executed on the annotations page (Annotation Text Column).

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 confidence

A stored Cross-Site Scripting (XSS) vulnerability exists in the annotations feature where an authenticated user with add/edit privileges can inject malicious JavaScript into the Annotation Text Column. When other users view the annotations page, the injected payload executes in their browser context.

MitigationImplement strict input validation and output encoding/escaping on the annotation text field to neutralize malicious scripts before storage and before rendering.

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
Messaging GatewayApplication
Affected:< 10.8

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Identify installed version of Symantec Messaging Gateway
    Access the SMG administration console and navigate to the About or System Health page to view the installed version number, or use the command line interface to query the version with 'smg --version' or equivalent version lookup command.
    Affected if The installed version is less than 10.8 (for example, 10.7.x, 10.6.x, or earlier).
  2. Verify annotations feature is enabled
    Log into the SMG administration console and navigate to the annotations configuration section, typically found under Content > Annotations or a similar path within the policy settings.
    Affected if The annotations feature is enabled and accessible to users.
  3. Confirm user access to annotation add/edit functions
    Check the user role permissions within SMG by reviewing the administrative roles or policy groups that grant add/edit privileges to the annotations feature.
    Affected if Authenticated users have add/edit privileges to the annotations feature (this includes admin users or custom roles with annotation permissions).
  4. Inspect annotation text field handling
    Review the web application configuration or HTML source of the annotations page to verify whether input validation and output encoding are applied to the Annotation Text Column field.
    Affected if Output encoding/escaping is not implemented on the annotation text field when rendered, allowing unsanitized input to be stored and displayed.

User is affected if they run Symantec Messaging Gateway version below 10.8 and the annotations feature is enabled for authenticated users with add/edit privileges, with the annotation text field lacking proper output encoding.

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

Implement strict input validation and output encoding/escaping on the annotation text field to neutralize malicious scripts before storage and before rendering.

Recommended fix High confidence

Messaging Gateway version 10.8 or later

  1. 1. Back up the current Messaging Gateway configuration and any critical data.
  2. 2. Review the release notes for version 10.8 to understand new features and any known issues.
  3. 3. Schedule a maintenance window for the upgrade.
  4. 4. Download the Messaging Gateway version 10.8 (or later) from support.broadcom.com.
  5. 5. Follow the official upgrade documentation to install version 10.8.
  6. 6. After upgrade, verify that the Messaging Gateway services are running correctly.
  7. 7. Log in and verify that the annotation feature (Content tab) functions correctly.
  8. 8. Validate that the XSS vulnerability is remediated by testing the annotation feature with potential XSS payloads.

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

Fix this in Messaging Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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