What is the severity of CVE-2006-1117?

CVE-2006-1117 is classified with a high severity due to the presence of testing options in the firmware that could introduce significant security risks.

How do I fix CVE-2006-1117?

To fix CVE-2006-1117, update the firmware to version V10 or later that removes the insecure testing options.

What products are affected by CVE-2006-1117?

CVE-2006-1117 affects various nCipher products, including nShield, nForce, netHSM, payShield, SecureDB, DSE200 Document Sealing Engine, and Time Source Master Clock.

Is CVE-2006-1117 still a concern for organizations using affected products?

Yes, CVE-2006-1117 remains a concern due to the potential exploitation of testing features in production environments.

Are there any workarounds for CVE-2006-1117?

The best workaround for CVE-2006-1117 is to ensure affected devices are updated to secure firmware versions and to limit exposure of these devices to untrusted networks.

Vulnerability/
CVE-2006-1117

low

2.6

CWE

NVD-CWE-Other

9/3/2006

7/8/2024

CVE-2006-1117

First published: Thu Mar 09 2006(Updated: )

nCipher firmware before V10, as used by (1) nShield, (2) nForce, (3) netHSM, (4) payShield, (5) SecureDB, (6) DSE200 Document Sealing Engine, (7) Time Source Master Clock (TSMC), and possibly other products, contains certain options that were only intended for testing and not production, which might allow remote attackers to obtain information about encryption keys and crack those keys with less effort than brute force.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Ncipher Securedb
Ncipher Time Source Master Clock
Ncipher Nforce
Ncipher Dse200 Document Sealing Engine
nCipher nCore
Ncipher Nshield
Ncipher Nethsm	=2.0
Ncipher Nethsm	=2.1.12_cam5
Ncipher Nethsm	=2.1
Ncipher Payshield

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2006-1117?
CVE-2006-1117 is classified with a high severity due to the presence of testing options in the firmware that could introduce significant security risks.
How do I fix CVE-2006-1117?
To fix CVE-2006-1117, update the firmware to version V10 or later that removes the insecure testing options.
What products are affected by CVE-2006-1117?
CVE-2006-1117 affects various nCipher products, including nShield, nForce, netHSM, payShield, SecureDB, DSE200 Document Sealing Engine, and Time Source Master Clock.
Is CVE-2006-1117 still a concern for organizations using affected products?
Yes, CVE-2006-1117 remains a concern due to the potential exploitation of testing features in production environments.
Are there any workarounds for CVE-2006-1117?
The best workaround for CVE-2006-1117 is to ensure affected devices are updated to secure firmware versions and to limit exposure of these devices to untrusted networks.

collector/nvd-historical
collector/nvd-index
agent/type
agent/remedy
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/severity
agent/author
agent/weakness
agent/last-modified-date
agent/event
agent/tags
agent/description
agent/first-publish-date
agent/source
vendor/ncipher
canonical/ncipher securedb
canonical/ncipher time source master clock
canonical/ncipher nforce
canonical/ncipher dse200 document sealing engine
canonical/ncipher ncore
canonical/ncipher nshield
canonical/ncipher nethsm
version/ncipher nethsm/2.0
version/ncipher nethsm/2.1.12_cam5
version/ncipher nethsm/2.1
canonical/ncipher payshield

Frequently Asked Questions

What is the severity of CVE-2006-1117?
CVE-2006-1117 is classified with a high severity due to the presence of testing options in the firmware that could introduce significant security risks.
How do I fix CVE-2006-1117?
To fix CVE-2006-1117, update the firmware to version V10 or later that removes the insecure testing options.
What products are affected by CVE-2006-1117?
CVE-2006-1117 affects various nCipher products, including nShield, nForce, netHSM, payShield, SecureDB, DSE200 Document Sealing Engine, and Time Source Master Clock.
Is CVE-2006-1117 still a concern for organizations using affected products?
Yes, CVE-2006-1117 remains a concern due to the potential exploitation of testing features in production environments.
Are there any workarounds for CVE-2006-1117?
The best workaround for CVE-2006-1117 is to ensure affected devices are updated to secure firmware versions and to limit exposure of these devices to untrusted networks.

CVE-2006-1117

Remedy

Remedy

Remedy

Remedy

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2006-1117?

How do I fix CVE-2006-1117?

What products are affected by CVE-2006-1117?

Is CVE-2006-1117 still a concern for organizations using affected products?

Are there any workarounds for CVE-2006-1117?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2006-1117?

How do I fix CVE-2006-1117?

What products are affected by CVE-2006-1117?

Is CVE-2006-1117 still a concern for organizations using affected products?

Are there any workarounds for CVE-2006-1117?