CVE-2004-1635: Medium severity Bugzilla vulnerability

Published Oct 24, 2004
·
Updated

Bugzilla 2.17.1 through 2.18rc2 and 2.19 from cvs, when using the insidergroup feature, does not sufficiently protect private attachments when there are changes to the metadata, such as filename, description, MIME type, or review flags, which allows remote authenticated users to obtain sensitive information when (1) viewing the bug activity log or (2) receiving bug change notification mails.

Affected Software

52 affected components
Bugzilla=2.17.6
Bugzilla=2.16.1
Bugzilla=2.18-rc1
Bugzilla=2.16.2
Bugzilla=2.17.4
Bugzilla=2.10
Bugzilla=2.17.1
Bugzilla=2.16
Bugzilla=2.14.2
Bugzilla=2.14.3
Bugzilla=2.14.4
Bugzilla=2.6
Bugzilla=2.17.5
Bugzilla=2.17.3
Bugzilla=2.4
Bugzilla=2.16.4
Bugzilla=2.12
Bugzilla=2.8
Bugzilla=2.16.3
Bugzilla=2.14.5
Bugzilla=2.17.7
Bugzilla=2.17
Bugzilla=2.18-rc2
Bugzilla=2.14.1
Bugzilla=2.16.5
Bugzilla=2.14
Bugzilla=2.4
Bugzilla=2.6
Bugzilla=2.8
Bugzilla=2.10
Bugzilla=2.12
Bugzilla=2.14
Bugzilla=2.14.1
Bugzilla=2.14.2
Bugzilla=2.14.3
Bugzilla=2.14.4
Bugzilla=2.14.5
Bugzilla=2.16
Bugzilla=2.16.1
Bugzilla=2.16.2
Bugzilla=2.16.3
Bugzilla=2.16.4
Bugzilla=2.16.5
Bugzilla=2.17
Bugzilla=2.17.1
Bugzilla=2.17.3
Bugzilla=2.17.4
Bugzilla=2.17.5
Bugzilla=2.17.6
Bugzilla=2.17.7
Bugzilla=2.18-rc1
Bugzilla=2.18-rc2

Remediation

Event History

Oct 24, 2004
CVE Published
04:00 AM
Feb 20, 2005
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2004-1635?

CVE-2004-1635 is considered to be a moderate severity vulnerability due to its potential for unauthorized access to sensitive information.

2

How do I fix CVE-2004-1635?

To fix CVE-2004-1635, upgrade to Bugzilla version 2.18 or later where the vulnerability is resolved.

3

What versions of Bugzilla are affected by CVE-2004-1635?

CVE-2004-1635 affects Bugzilla versions from 2.17.1 to 2.18rc2.

4

What type of attack does CVE-2004-1635 allow?

CVE-2004-1635 allows remote authenticated users to gain unauthorized access to private attachments by manipulating metadata.

5

Is there a workaround for CVE-2004-1635?

No official workaround is available for CVE-2004-1635; upgrading to a patched version is the recommended solution.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203