dbcve.org
Obs ServerApplication

CVE-2010-3782

HIGH · 8.8 CVSS v3.1 Published 2020-01-02
Fix available
A fix is available. Upgrade to 1.7.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
obs-server before 1.7.7 allows logins by 'unconfirmed' accounts due to a bug in the REST api implementation.

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

obs-server before version 1.7.7 contains a bug in its REST API implementation that allows authentication using 'unconfirmed' accounts. This authentication bypass occurs because the REST API fails to properly validate account confirmation status during the login process, permitting access to accounts that should not yet be active.

MitigationUpgrade obs-server to version 1.7.7 or later to obtain the patch that properly validates account confirmation status in the REST API authentication flow.

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
Obs ServerApplication
Affected:< 1.7.7
Linux Enterprise ServerOperating system
Affected:= 11

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 obs-server installation and version
    Run 'rpm -q obs-server' or check the package manager for obs-server installation. Use 'obs-server -v' or check /usr/lib/obs/server/version if available.
    Affected if Version is lower than 1.7.7 (e.g., 1.7.6, 1.7.5, etc.)
  2. Confirm SLE 11 environment
    Run 'cat /etc/os-release' or 'cat /etc/SuSE-release' to verify the operating system version.
    Affected if Running Suse Linux Enterprise Server version 11 with obs-server installed
  3. Check if REST API is enabled
    Inspect the obs-server configuration file (typically in /etc/obs/server.conf or similar) for API-related settings. Look for parameters like 'enable_api', 'api_host', or 'rest_api_mode'.
    Affected if REST API is explicitly enabled in the server configuration
  4. Identify unconfirmed user accounts
    Query the obs-server database or user configuration to list accounts with unconfirmed status. Check for users where the 'confirmed' field is false or 'state' indicates 'unconfirmed'.
    Affected if There are user accounts marked as unconfirmed in the system
  5. Verify API authentication behavior
    Attempt to authenticate via the REST API endpoint (e.g., POST to /login or /auth) using credentials from an unconfirmed account. Check if the API returns a valid session token.
    Affected if The REST API accepts authentication and returns a session for an unconfirmed account

You are affected if obs-server version is below 1.7.7, the REST API is enabled, and unconfirmed user accounts exist in the system, allowing them to authenticate when they should not be able to.

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.

From vendor data
Upgrade available Upgrade to 1.7.7 or later
Fixed in 1.7.7
Interim mitigation

Upgrade obs-server to version 1.7.7 or later to obtain the patch that properly validates account confirmation status in the REST API authentication flow.

Fix this in Obs Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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