CVE-2007-0310
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 · uneditedBMC Remedy Action Request System 5.01.02 Patch 1267 generates different error messages for failed login attempts with a valid username than for those with an invalid username, which allows remote attackers to determine valid account names.
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 · high confidenceThe BMC Remedy Action Request System 5.01.02 Patch 1267 reveals whether usernames are valid by returning different error messages for failed login attempts. When a valid username is used with an incorrect password, the system returns a different error than when an invalid username is used. This allows remote attackers to enumerate valid user accounts through repeated login attempts.
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= 5.01.02_patch_1267CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed BMC Remedy ARS versionCheck the installed BMC Remedy Action Request System version on the server. On Windows, check the program files or AR System installation directory for version information. On Linux/Unix, check /opt/bmc/ARSystem or the installation path for version files or run: arschema -v or aradmin -versionAffected if The installed version is exactly 5.01.02_patch_1267 (specific patch level)
-
Verify login interface is accessibleAttempt to access the BMC Remedy web login page (typically at /arsys/forms or /armaster) using a web browser or curl commandAffected if The login page responds and accepts authentication attempts
-
Test login with invalid usernameSubmit a login attempt using a clearly invalid username such as 'nonexistentuser123' with any password. Capture the exact error message returned by the systemAffected if The system returns an error message (e.g., 'User does not exist' or similar)
-
Test login with valid username and wrong passwordSubmit a login attempt using a known valid username (or test with common default accounts like 'Demo' or 'Administrator') but provide an incorrect password. Capture the exact error message returnedAffected if The system returns an error message that differs from the invalid username error
-
Compare error message responsesVisually compare the error messages from step 3 and step 4. Look for differences in wording, timing, or any indication that the system distinguishes between valid and invalid usernamesAffected if The error messages are different, confirming the username enumeration vulnerability exists
A user is affected if they are running BMC Remedy Action Request System version 5.01.02_patch_1267 AND the login page returns distinct error messages for valid vs invalid usernames, allowing an attacker to enumerate valid user accounts.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataModify the login failure handler to return a consistent, generic error message (e.g., 'Invalid credentials') for all failed authentication attempts, regardless of whether the username exists.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0310 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-0310 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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