What is the severity of CVE-2006-1298?

CVE-2006-1298 has a moderate severity rating due to the potential for remote code execution.

How do I fix CVE-2006-1298?

To fix CVE-2006-1298, apply the latest patches and updates available for Veritas Backup Exec.

Which versions are affected by CVE-2006-1298?

CVE-2006-1298 affects Veritas Backup Exec 9.1 and 10.0 for Windows Servers.

What are the potential impacts of CVE-2006-1298?

The potential impacts of CVE-2006-1298 include unauthorized access and execution of arbitrary code.

Is CVE-2006-1298 still relevant today?

While CVE-2006-1298 is an older vulnerability, it may still be relevant for systems running affected versions of Backup Exec that have not been updated.

Vulnerability/
CVE-2006-1298

medium

4.6

CWE

NVD-CWE-Other

19/3/2006

7/8/2024

CVE-2006-1298

First published: Sun Mar 19 2006(Updated: )

Format string vulnerability in the Job Engine service (bengine.exe) in the Media Server in Veritas Backup Exec 10d (10.1) for Windows Servers rev. 5629, Backup Exec 10.0 for Windows Servers rev. 5520, Backup Exec 10.0 for Windows Servers rev. 5484, and Backup Exec 9.1 for Windows Servers rev. 4691, when the job log mode is Full Detailed (aka Full Details), allows remote authenticated users to cause a denial of service and possibly execute arbitrary code via a crafted filename on a machine that is backed up by Backup Exec.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Symantec Veritas Backup Exec	=9.1
Symantec Veritas Backup Exec	=10.0

Remedy

http://support.veritas.com/docs/282254

Remedy

http://www.securityfocus.com/bid/17096

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2006-1298?
CVE-2006-1298 has a moderate severity rating due to the potential for remote code execution.
How do I fix CVE-2006-1298?
To fix CVE-2006-1298, apply the latest patches and updates available for Veritas Backup Exec.
Which versions are affected by CVE-2006-1298?
CVE-2006-1298 affects Veritas Backup Exec 9.1 and 10.0 for Windows Servers.
What are the potential impacts of CVE-2006-1298?
The potential impacts of CVE-2006-1298 include unauthorized access and execution of arbitrary code.
Is CVE-2006-1298 still relevant today?
While CVE-2006-1298 is an older vulnerability, it may still be relevant for systems running affected versions of Backup Exec that have not been updated.

collector/nvd-historical
collector/nvd-index
agent/references
agent/type
agent/softwarecombine
agent/remedy
collector/mitre-cve
source/MITRE
agent/author
agent/last-modified-date
agent/weakness
agent/severity
agent/tags
agent/event
agent/first-publish-date
agent/description
agent/source
vendor/symantec veritas
canonical/symantec veritas backup exec
version/symantec veritas backup exec/9.1
version/symantec veritas backup exec/10.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2006-1298?
CVE-2006-1298 has a moderate severity rating due to the potential for remote code execution.
How do I fix CVE-2006-1298?
To fix CVE-2006-1298, apply the latest patches and updates available for Veritas Backup Exec.
Which versions are affected by CVE-2006-1298?
CVE-2006-1298 affects Veritas Backup Exec 9.1 and 10.0 for Windows Servers.
What are the potential impacts of CVE-2006-1298?
The potential impacts of CVE-2006-1298 include unauthorized access and execution of arbitrary code.
Is CVE-2006-1298 still relevant today?
While CVE-2006-1298 is an older vulnerability, it may still be relevant for systems running affected versions of Backup Exec that have not been updated.