dbcve.org
OpensuseOperating system

CVE-2013-1090

HIGH · 7.2 CVSS v2.0 Published 2013-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
No privileges 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
The SUSE horde5 package before 5.0.2-2.4.1 sets incorrect ownership for certain configuration files and directories including /etc/apache2/vhosts.d, which allows local wwwrun users to gain privileges via unspecified vectors.

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 confidence

The SUSE horde5 package before version 5.0.2-2.4.1 sets incorrect ownership on configuration files and directories, specifically /etc/apache2/vhosts.d. This allows local users running as the wwwrun (Apache) account to gain elevated privileges through unspecified vectors by exploiting the misconfigured file permissions.

MitigationCorrect ownership permissions on /etc/apache2/vhosts.d and related configuration files, ensuring wwwrun does not have inappropriate access. Update to horde5 version 5.0.2-2.4.1 or later which contains the proper fix.

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
OpensuseOperating system
Affected:= 12.3

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
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:C/I:C/A:C

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. Check if horde5 package is installed
    Run: rpm -q horde5 or dpkg -l | grep horde5 (depending on system)
    Affected if horde5 package is installed and version is before 5.0.2-2.4.1
  2. Identify the operating system version
    Run: cat /etc/os-release or lsb_release -r
    Affected if System is Opensuse 12.3 and horde5 is installed with vulnerable version
  3. Verify ownership of /etc/apache2/vhosts.d
    Run: ls -la /etc/apache2/vhosts.d
    Affected if The directory /etc/apache2/vhosts.d is owned by wwwrun or has permissions allowing wwwrun inappropriate write access
  4. Check horde5 package version
    Run: rpm -qi horde5 or dpkg -s horde5
    Affected if Installed version is less than 5.0.2-2.4.1

You are affected if you are running Opensuse 12.3 with horde5 package installed at a version earlier than 5.0.2-2.4.1 and /etc/apache2/vhosts.d is owned or writable by the wwwrun user.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Correct ownership permissions on /etc/apache2/vhosts.d and related configuration files, ensuring wwwrun does not have inappropriate access. Update to horde5 version 5.0.2-2.4.1 or later which contains the proper fix.

Fix this in Opensuse Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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